Backport of UI: better calculation for advanced secret in KV v2 into release/1.15.x #24525
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/24504-enhancement-for-kv-engine-ui-behavior/preferably-just-dane
branch
from
066fcca to
e653cc8
Compare
github-actions
bot
added
the
hashicorp-contributed-pr
hashishaw
approved these changes
Dec 13, 2023
hashishaw
deleted the
backport/24504-enhancement-for-kv-engine-ui-behavior/preferably-just-dane
branch
|
Build Results: |
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 #24513 to be assessed for backporting due to the inclusion of the label backport/1.15.x.
The below text is copied from the body of the original PR.
In #24308 we inadvertently introduced an issue where secrets with values that include
{would be locked to the JSON view. This PR makes the check in a more intelligent way so that the original intended behavior is preserved, but secret values are not shown.Now, string values with
{are shown as inputs instead of with the JSON editor:Out of scope for this backport but as a future improvement, we will add obscurity to the JSON view that is toggleable
Overview of commits