-
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
Bug fix: Update KV data when you change the version of a nested secret #25152
Merged
Monkeychip
merged 9 commits into
main
from
ui/VAULT-23660/nested-secret-version-dropdown
Feb 1, 2024
Merged
Bug fix: Update KV data when you change the version of a nested secret #25152
Monkeychip
merged 9 commits into
main
from
ui/VAULT-23660/nested-secret-version-dropdown
Feb 1, 2024
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
github-actions
bot
added
the
hashicorp-contributed-pr
If the PR is HashiCorp (i.e. not-community) contributed
label
Jan 31, 2024
Build Results: |
hellobontempo
approved these changes
Jan 31, 2024
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.
These look good to me. In the PR description it might be worth including this resolves a regression introduced by #24224 which is why we're backporting to 1.15
revert accidental next step
2 tasks
Monkeychip
added a commit
that referenced
this pull request
Feb 5, 2024
#25152) * wip need to address testing but want to test something quick on 1.13 * add test coverage * changelog * update test comment * rename getter * Update kv-data-fields.hbs revert accidental next step * linting things
Monkeychip
added a commit
that referenced
this pull request
Feb 7, 2024
#25152) * wip need to address testing but want to test something quick on 1.13 * add test coverage * changelog * update test comment * rename getter * Update kv-data-fields.hbs revert accidental next step * linting things
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Used to indicate a potential bug
hashicorp-contributed-pr
If the PR is HashiCorp (i.e. not-community) contributed
secret/kv
ui
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.
Fixes #25029.
Regression caused by #24224
This was caused because we were using a tracked property (
this.codeMirrorSring
) for the secret data and we needed a getter that relied on thethis.args.secret
model arg. The secret model was updating and thus thesecretData
was correct behind the scenes but the tracked property was not re-firing because it didn't rely on anything that was triggering a re-fire of the property.