You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
With a large team, there might be multiple people editing the same secret at the same time. If the page hasn't been reloaded, Vault gives you a 'check-and-set parameter did not match the current version' error by default, but if it is reloaded, it just gives you a warning, and let's you override the latest secret. Often overriding is done by accident since the url will open the version of the secret that was the latest at the time the link was clicked.
Describe the solution you'd like
Instead of just putting up a warning, let's make the user acknowledge that they are overriding the latest version of a secret by clicking a checkbox.
Describe alternatives you've considered
No other ones yet.
Explain any additional use-cases
Additional context
Previous:
Proposed:
Video ScreenshotScreen.Recording.2025-02-21.at.11.23.13.AM.mov
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
With a large team, there might be multiple people editing the same secret at the same time. If the page hasn't been reloaded, Vault gives you a 'check-and-set parameter did not match the current version' error by default, but if it is reloaded, it just gives you a warning, and let's you override the latest secret. Often overriding is done by accident since the url will open the version of the secret that was the latest at the time the link was clicked.
Describe the solution you'd like
Instead of just putting up a warning, let's make the user acknowledge that they are overriding the latest version of a secret by clicking a checkbox.
Describe alternatives you've considered
No other ones yet.
Explain any additional use-cases
Additional context


Previous:
Proposed:
Video Screenshot
Screen.Recording.2025-02-21.at.11.23.13.AM.mov
The text was updated successfully, but these errors were encountered: