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

Override TLS flags individually for meta commands #11592

Merged
merged 2 commits into from
Dec 1, 2021

Conversation

DerekStrickland
Copy link
Contributor

@DerekStrickland DerekStrickland commented Nov 30, 2021

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 would
get overwritten with blank strings.

Copy link
Member

@tgross tgross left a comment

Choose a reason for hiding this comment

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

LGTM

command/meta.go Outdated Show resolved Hide resolved
Co-authored-by: Tim Gross <[email protected]>
@vercel vercel bot temporarily deployed to Preview – nomad December 1, 2021 17:07 Inactive
@DerekStrickland DerekStrickland merged commit 189806f into main Dec 1, 2021
@DerekStrickland DerekStrickland deleted the b-gh-11460-tls-skip-verify branch December 1, 2021 17:07
lgfa29 pushed a commit that referenced this pull request Jan 17, 2022
* Override TLS flags individually for meta commands

* Update command/meta.go

Co-authored-by: Tim Gross <[email protected]>

Co-authored-by: Tim Gross <[email protected]>
lgfa29 pushed a commit that referenced this pull request Jan 17, 2022
* Override TLS flags individually for meta commands

* Update command/meta.go

Co-authored-by: Tim Gross <[email protected]>

Co-authored-by: Tim Gross <[email protected]>
@github-actions
Copy link

github-actions bot commented Nov 3, 2022

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.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tls-skip-verify may not work on nomad monitor
3 participants