-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow full range of log levels #119
Conversation
Co-authored-by: Andras Beni <[email protected]>
Co-authored-by: Andras Beni <[email protected]>
Thanks for the review @andrasbeni — applied your suggestions. |
Use: "oxia", | ||
Short: "Short description", | ||
Long: `Long description`, | ||
PreRunE: configureLogLevel, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could also call the common.ConfigureLogger()
from this hook
// LogDebug Used for flags | ||
LogDebug bool | ||
// LogLevel Used for flags | ||
LogLevel zerolog.Level |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(for a different PR) Should we also improve the LogJson
argument to make it a kind of --log-format json|text|....
?
Co-authored-by: Dave Maughan <[email protected]>
Motivation
Sometimes info and debug is not enough.
Changes
-d
flag from CLI-l
flag to permit usage of any one of the rs/zerolog levelsinfo
as before