#807: Mark api_key as sensitive data#853
Draft
nielstholenaar wants to merge 10 commits intoDataDog:mainfrom
Draft
#807: Mark api_key as sensitive data#853nielstholenaar wants to merge 10 commits intoDataDog:mainfrom
nielstholenaar wants to merge 10 commits intoDataDog:mainfrom
Conversation
nielstholenaar
force-pushed
the
feature/807-api-as-sensitive
branch
from
580d252 to
83f35a1
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this PR do?
Closes: #807
Motivation
Increase security by not including sensitive data in Logs and File diffs.
Additional Notes
This PR results in a breaking change, as it is required to pass the api_key param as sensitive.