[events] Retain Secret values.
#9351
Merged
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
Instead of replacing `Secret` values with the text `[secret]`, retain the `Secret` value and replace its element with the text `[secret]`. This allows downstream consumers (e.g. the CLI's diff renderer) to understand that the contents of the value is secret if necessary.
pgavlin
commented
Apr 5, 2022
Frassle
approved these changes
Apr 6, 2022
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.
Instead of replacing
Secretvalues with the text[secret], retainthe
Secretvalue and replace its element with the text[secret].This allows downstream consumers (e.g. the CLI's diff renderer) to
understand that the contents of the value is secret if necessary.
Concretely, this fixes an issue in which differences in nested
properties of secret object values would not render correctly.