-
Notifications
You must be signed in to change notification settings - Fork 4.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
UI: remove default setting for max_versions
in kv metadata
#22394
Conversation
Build Results: |
CI Results: |
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.
Thanks for tackling. Backport as far as to 1.12?
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.
Thank you for the detailed description!
* remove default setting for max versions - leave unset with a value of 0 * add changelog
The default value of a secret's metadata was incorrectly setting
max_versions
to 10 which caused unintended side effects. This PR fixes #8656. Instead of setting the metadata'smax_versions
from the engine's config, leaving unset has the same result without manipulating any values under the hood.The greater number takes precedence if both the engine and secret metadata have
max_versions
configured. Otherwise,0
means unset and if neither have amax_versions
value, Vault will keep the 10 latest versions.max_versions
so the metadata value is usedmax_versions
is unset so the engine's value is usedmax_versions
numberBoth metadata
READ
responses below have the same kv engine config: