-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Override TLS flags individually for meta commands #11592
Conversation
1ac9424
to
fe5c7c3
Compare
fe5c7c3
to
8e6c989
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
Co-authored-by: Tim Gross <tgross@hashicorp.com>
* Override TLS flags individually for meta commands * Update command/meta.go Co-authored-by: Tim Gross <tgross@hashicorp.com> Co-authored-by: Tim Gross <tgross@hashicorp.com>
* Override TLS flags individually for meta commands * Update command/meta.go Co-authored-by: Tim Gross <tgross@hashicorp.com> Co-authored-by: Tim Gross <tgross@hashicorp.com>
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
This block used to set the entire config.TLSConfig with the
values passed by the user. This worked fine if the user set all the options,
or at least enough, but had the unintended side effect of overwriting values
that had been configured in environment variables. If the user passed only
one setting, say
tls-skip-verify
, all the other settings, like CACert wouldget overwritten with blank strings.