You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation for NewClient suggests that dns:/// is correct, but that causes the authority to be empty, making it impossible for anyone using a custom authority to configure a custom authority
The text was updated successfully, but these errors were encountered:
This allows users to continue using the recommended dns://authority/host:port notation
when needing to specify a custom authority.
Fixesopen-telemetry#10449
Signed-off-by: Alex Boten <[email protected]>
The validation that was added for
dns:///
makes it impossible for end users to use dns resolution as documented here: https://github.com/grpc/grpc/blob/master/doc/naming.md#detailed-designThe documentation for NewClient suggests that
dns:///
is correct, but that causes theauthority
to be empty, making it impossible for anyone using a custom authority to configure a custom authorityThe text was updated successfully, but these errors were encountered: