fix: OB-37389 Obfuscate secrets in YAML body #101
Merged
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.
Add whole processor framework to modify an event body in place. The set of actions that do that are also type-specific, meaning that we only run relevant actions on any given event, based on the object type.
These actions modify the unmarshalled object IN PLACE and BEFORE the attributes-computing actions do their thing. This is mainly to allow secrets' obfuscation, where we want to prevent secret stuff to end up in the attributes by mistake.
Add secret "body" actions that obfuscate the secrets in "data".
Description
OB-XXX Please explain the changes you made here.
Checklist