-
Notifications
You must be signed in to change notification settings - Fork 782
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
Versioned KV support #1180
Versioned KV support #1180
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.
Minor docs comments but otherwise 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.
One more small thought on the readme!
3caa27a
to
3f4e28f
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.
Looks great!
When making unauthenticated secret lookup requests, ignore errors that result from checking the secret mount type. If it's a persistent error, the error on the actual lookup. This restores behavior to before hashicorp#1180 . A nomad enterprise customer hit this regression.
When making unauthenticated secret lookup requests, ignore errors that result from checking the secret mount type. If it's a persistent error, the error on the actual lookup. This restores behavior to before hashicorp#1180 .
When vault.read fails to determine whether a path is KVv2, assume it's KVv1 and read from the path as passed from user. Here we fallback to behavior prior to hashicorp#1180, so KVv2 check is for enhancement only. If user truely lacks access, the secret lookup call would fail and we report error back. A customer hit a regression after they upgraded nomad with updated consul-template, where their templates failed to read approle info because isKVv2 returned an error. The case is reproduced in `TestVaultReadQuery_Fetch_NonSecrets` test.
This PR adds support for reading secrets from the v2 KV secrets engine in Vault.
Fixes #1121
Fixes #1146