This repository was archived by the owner on Sep 11, 2025. It is now read-only.
Reduce logging level for secrets #190
Merged
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
…troubleshooting you wont see container configurations during a deploy.
|
Seems reasonable to me, would like @intjonathan to chime in as well. |
|
I'd like to still print a subset at Then at |
… of successfully starting.
MidnightsFX
commented
Dec 4, 2018
intjonathan
approved these changes
Dec 4, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Deployments will no longer show container configurations unless you set a lower logging level. This should hide secrets which are passed to containers at startup.
You can continue to view secrets for production deploys by turning up your log level.