automod: ability to surpress canonical-log-line verbosity when developing #492
Conversation
This file contains 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
…ping The behavior with this CLI flag set is that most log lines end up being "DEBUG" not "INFO", and won't print by default. This is more useful for development when actually inspecting logs visually.
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.
The behavior with this CLI flag set is that most log lines end up being "DEBUG" not "INFO", and won't print by default. This is more useful for development when actually inspecting logs visually.
I'm not actually sure this is the right way forward. Maybe instead the canonical log line should have a fixed verbosity and we do something closer to the slack webhook for at a higher log level?