-
Notifications
You must be signed in to change notification settings - Fork 106
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
Set VaultConnection headers on the vault client #629
Conversation
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
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.
Looking good. I added a suggestion to ensure that the Vault namespace from config always takes precedence over. We may also want to warn in the case where X-Vault-Namespace
is being set in the custom headers. We could also make setting that header illegal.
Thanks! |
Set Vault client headers from VaultConnection.Spec.Headers.
Fixes #622