-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[Streaming][bugfix] handle TLS signalisation when TLS is disabled on client side (alternative to #9494) #9512
[Streaming][bugfix] handle TLS signalisation when TLS is disabled on client side (alternative to #9494) #9512
Conversation
…client side Tnis is an alternative to hashicorp#9494
8a03283
to
e2f2d4b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! looks good! Do you think it would be possible to write a test for newDialer
that fails without this change? I think there is an integration test somewhere in the agent/grpc
package that uses fakeRPCListener
that might work.
This ensures that hashicorp#9474 will not reproduce.
c5a2e3a
to
994fe80
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Those integration tests seem to be failing on master, so not related to this change. |
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/305585. |
🍒✅ Cherry pick of commit 326a312 onto |
[Streaming][bugfix] handle TLS signalisation when TLS is disabled on client side (alternative to #9494)
Tnis is an alternative to #9494
We just patch the GRPC side, not everything as suggested by @dnephin