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 support for TLSServerName for HTTP health checks #116

Merged
merged 1 commit into from
Jan 24, 2022

Conversation

RadekDvorak
Copy link
Contributor

This enables custom SNI/TLSServerName for HTTP health checks. This is essentially a followup for #102.

Signed-off-by: Radek Dvořák <radek.dvorak@gmail.com>
@RadekDvorak RadekDvorak requested a review from a team December 15, 2021 13:00
@hashicorp-cla
Copy link

hashicorp-cla commented Dec 15, 2021

CLA assistant check
All committers have signed the CLA.

@eikenb
Copy link
Contributor

eikenb commented Jan 24, 2022

Thanks for submitting this @RadekDvorak! Nice followup with consul having accepted the upstream fixes.

And thanks for the code review @cbroglie! I'm new to maintaining this project and am not as familiar with the code. Knowing this does address/fix your issue is good information.

Copy link
Contributor

@eikenb eikenb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@eikenb eikenb added this to the v0.7.0 milestone Jan 24, 2022
@eikenb eikenb merged commit c3446d4 into hashicorp:master Jan 24, 2022
cbroglie added a commit to cbroglie/consul-esm that referenced this pull request Sep 20, 2022
Support for `TLSServerName` was added in hashicorp#116, but this early return
equality check wasn't updated to include the new field. The impact is
changes to the value of `TLSServerName` aren't picked up by the health
checks unless accompanied by other changes to the check definition.
eikenb pushed a commit that referenced this pull request Sep 20, 2022
Support for `TLSServerName` was added in #116, but this early return
equality check wasn't updated to include the new field. The impact is
changes to the value of `TLSServerName` aren't picked up by the health
checks unless accompanied by other changes to the check definition.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants