fix(logs/secrets): check for disallowed/non-existent secrets #274
Conversation
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
Codecov Report
@@ Coverage Diff @@
## v0.12.1 #274 +/- ##
===========================================
+ Coverage 77.62% 77.67% +0.05%
===========================================
Files 67 67
Lines 4875 4873 -2
===========================================
+ Hits 3784 3785 +1
+ Misses 950 948 -2
+ Partials 141 140 -1
|
wass3r
approved these changes
Feb 21, 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.
Backport for patch release (v0.12.1).
When users inject secrets for a container that are not allowed for the event or simply do not exist, the
getSecretValuesfunction would set them to an empty string, resulting in ugly logs.Earlier, merged PR: #272