Backport of UI/Only show form values if have read access into release/1.10.x #14853
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-secure-vault-core
force-pushed
the
backport/ui/update-no-read-kv-secret-bug/annually-intense-poodle
branch
from
d49f7e5
to
72ea32a
Compare
…et-bug/annually-intense-poodle
…et-bug/annually-intense-poodle
|
Closing because when binary testing, this change did not resolve the original issue |
hellobontempo
deleted the
backport/ui/update-no-read-kv-secret-bug/annually-intense-poodle
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #14794 to be assessed for backporting due to the inclusion of the label backport/1.10.x.
The below text is copied from the body of the original PR.
This is a bug fix for when a user without read capabilities (but has update), creates a new version of a secret, then goes back to the previous version and clicks "Create new version+" and the recently created secret is populated in the form fields. Even though the user doesn't have read access - it was cached in the browser from the put request when the user updated the secret