feat: support custom name resolver #1202
Open
+48
−5
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
raflFaisal
force-pushed
the
support-custom-name-resolver
branch
from
f27db24 to
0497bd8
Compare
Signed-off-by: raflFaisal <[email protected]>
raflFaisal
force-pushed
the
support-custom-name-resolver
branch
from
0497bd8 to
cfc030f
Compare
beeme1mr
approved these changes
Feb 4, 2025
Signed-off-by: raflFaisal <[email protected]>
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 PR
To provide a :authority header to request route to target backend services using default_authority parameter by the JS clients. This enable better integration with service proxies like Envoy, facilitating more flexible and robust gRPC client configurations.
Related Issues
#1187
open-feature/flagd#1532
How to test
Use defaultAuthority parameter to pass down the target authority when sending a grpc request from client side.