Skip to content

fix: OB-37389 Obfuscate secrets in YAML body #101

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

Merged
merged 1 commit into from
Oct 4, 2024

Conversation

obs-gh-enricogiorio
Copy link
Collaborator

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

  • Created tests which fail without the change (if possible)
  • Extended the README / documentation, if necessary

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".
@obs-gh-enricogiorio obs-gh-enricogiorio merged commit b6e28d6 into main Oct 4, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants