-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Added support for VAULT_PROXY_ADDR + Updated docs #15377
Added support for VAULT_PROXY_ADDR + Updated docs #15377
Conversation
Updated documentation to describe the behavior when supplying `VAULT_HTTP_PROXY`. Also added support for `VAULT_PROXY_ADDR` as a 'better name' for `VAULT_HTTP_PROXY`.
Change is in addition to existing change
Related to GH issue raised regarding behavior for Vault proxy env var.
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.
minor nits; but LGTM. I'm not sure if you require other reviewers since there seems to be new code introduced.
Co-authored-by: Loann Le <[email protected]>
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.
I'm not 100% convinced that the better name is worth having two different ways to do something and the potential confusion that introduces. That said, I like the tests and the docs, and my minor misgivings aren't enough for me to reject this. Perhaps in time we could retire the old name.
As raised in a PR comment, we don't need to call ReadEnvironment() as the DefaultConfig() does that for us. We can just check the config.Error for the error.
Yes, ideally we could get rid of the |
Updated documentation to describe the behavior when supplying `VAULT_HTTP_PROXY`. Also added support for `VAULT_PROXY_ADDR` as a 'better name' for `VAULT_HTTP_PROXY`.
Updated documentation to describe the behavior when supplying
VAULT_HTTP_PROXY
.Also added support for
VAULT_PROXY_ADDR
as a 'better name' forVAULT_HTTP_PROXY
.