Skip to content

Plumb through option for configuring DNS resolver#1501

Open
Sushisource wants to merge 2 commits intomainfrom
set-dns-optiuons
Open

Plumb through option for configuring DNS resolver#1501
Sushisource wants to merge 2 commits intomainfrom
set-dns-optiuons

Conversation

@Sushisource
Copy link
Copy Markdown
Member

What was changed

Plumb through the DNS resolver options to core

Why?

Nice to be able to disable this

Checklist

  1. Closes

  2. How was this tested:
    Added config unit test

  3. Any docs updates needed?

@Sushisource Sushisource requested a review from a team as a code owner May 5, 2026 19:25
Comment on lines +248 to +252
let dns_load_balancing = if has_proxy {
None
} else {
self.dns_load_balancing_config.map(Into::into)
};
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this might be handled elsewhere but what if a user has configured both a proxy and a dns balancing policy? do we just silently drop the config? do we log a warning? mostly asking out of curiosity.

Comment thread tests/test_service.py
assert bridge_config.dns_load_balancing_config.resolution_interval_millis == 5000


def test_connect_config_dns_load_balancing_disabled():
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

related to my question about the proxy taking precedence over dns config: is that behavior tested in core?

@cconstable
Copy link
Copy Markdown
Contributor

lgtm 👍 do the other sdks need this update? seems like a useful config to have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants