-
Notifications
You must be signed in to change notification settings - Fork 109
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
Plugin logging on registration can't be made silent #86
Comments
so my current workaround is to have a custom plugin/import that does:
This is fragile as Go doesn't guaratee init() ordering in this case, afaik. |
for an example of how it could look like, see how we register plugins in another project, https://github.com/facebookincubator/contest/blob/master/cmds/contest/main.go#L90 |
@elmarco can you try with the latest commit? Now setting the log level globally should not print the plugin loading messages anymore. We can also add a CLI flag for the purpose |
Calling CoreDHCP with -quiet will disable logging entirely. Fixes #86 Signed-off-by: Andrea Barberio <insomniac@slackware.it>
works for me, thanks |
And removed -debug flag. Now all the logging levels can be specified with -loglevel. "none" is a special log level that disables logging altogether. Fixes #86 Signed-off-by: Andrea Barberio <insomniac@slackware.it>
And removed -debug flag. Now all the logging levels can be specified with -loglevel. "none" is a special log level that disables logging altogether. Fixes #86 Signed-off-by: Andrea Barberio <insomniac@slackware.it>
And removed -debug flag. Now all the logging levels can be specified with -loglevel. "none" is a special log level that disables logging altogether. Fixes #86 Signed-off-by: Andrea Barberio <insomniac@slackware.it>
And removed -debug flag. Now all the logging levels can be specified with -loglevel. "none" is a special log level that disables logging altogether. Fixes #86 Signed-off-by: Andrea Barberio <insomniac@slackware.it>
Hi,
When the plugins are init(), they log the registration:
Unfortunately, I can't see a way to silent it, since init() is called early, before the program has the chance to change logrus behaviour. Please advise.
The text was updated successfully, but these errors were encountered: