feat: logs non-secret env variables on startup - #164
Merged
Merged
Conversation
simon-20
requested changes
Aug 10, 2026
simon-20
left a comment
simon-20
left a comment
Contributor
There was a problem hiding this comment.
Hi Andrew, thanks for this, comments in line below
Contributor
Author
|
Many thanks for this @simon-20 |
simon-20
approved these changes
Aug 25, 2026
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
2 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.
The configuration is now written to the log when the service is run. Each configuration variable in
config.pycarries a flag marking whether its value may be logged: so a variable added in future is private unless it is explicitly markedLOGGABLE.The settings which come from the command line are logged too.
Current flags are my best guess.