Backport of UI: remove default setting for max_versions
in kv metadata into release/1.14.x
#22405
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #22394 to be assessed for backporting due to the inclusion of the label backport/1.14.x.
The below text is copied from the body of the original PR.
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:Overview of commits