Add redactedKeys for removing sensitive values from metadata #540
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.
Goal
Adds the
redactedKeys
property toConfiguration
which allows a user to specify sensitive keys. Any sensitive values present in the metadata ofBugsnagEvent
will be replaced by"[REDACTED]"
when serialized to JSON.Changeset
redactedKeys
property toConfiguration
, which by default is an array of "password"redactedKeys
on eachBugsnagEvent
using theConfiguration
valueBugsnagEvent
now redacts sensitive values with any key that is considered redactedTests
redactedKeys
and its effect on JSON serialization