-
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: better calculation for advanced secret in KV v2 #24513
Conversation
Build 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.
do we need a test accounting for escape characters/multi line entries \
? I remember this coming up somewhere 🤔
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 and adding test coverage!
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