Scope clients to new hosts #42
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andrewstucki
force-pushed
the
scoped-clients
branch
from
4f38500 to
dd0ee0c
Compare
andrewstucki
force-pushed
the
scoped-clients
branch
from
dd0ee0c to
4e13468
Compare
RafalKorepta
approved these changes
Dec 4, 2024
bojand
approved these changes
Dec 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows for creating a "scoped" client that talks only to the given broker, but with the same TLS and auth settings as the previous client. It adds methods for scoping a client to a broker by host URL and for scoping via Broker ID.