Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GRPC dial options support to etcd cluster options #4066

Merged
merged 1 commit into from
Feb 9, 2022

Conversation

andrewmains12
Copy link
Contributor

What this PR does / why we need it:

GRPC dial options are useful for a variety of use cases--adding default headers (via a stream interceptor), injecting code into the low level connection flow via
a net.Dialer (e.g. to support proxying across network boundaries).

This diff adds an option on clusters to pass through GRPC.DialOptions for these use cases. Defaults of nil should match current behavior.

Does this PR introduce a user-facing and/or backwards incompatible change?:

NONE

Does this PR require updating code package or user-facing documentation?:

NONE

GRPC dial options are useful for a variety of use cases--adding default headers (via a stream interceptor), injecting code into the low level connection flow via
a net.Dialer (e.g. to support proxying across network boundaries).

This diff adds an option on clusters to pass through GRPC.DialOptions for these use cases. Defaults of nil should match current behavior.
@andrewmains12 andrewmains12 merged commit bdada60 into master Feb 9, 2022
@andrewmains12 andrewmains12 deleted the amains/etcd_dial_options branch February 9, 2022 21:14
andrewmains12 added a commit that referenced this pull request Feb 24, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 24, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 24, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 24, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 24, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 25, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 25, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 25, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 25, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 28, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 28, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
andrewmains12 added a commit that referenced this pull request Feb 28, 2022
Similar idea to #4066, except for m3msg, and specific to allowing customization of net.Dial behavior. This is useful for e.g.
proxying across network boundaries.
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