Bug fix: Update KV data when you change the version of a nested secret #25152
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.