-
Notifications
You must be signed in to change notification settings - Fork 579
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
Log levels broken #292
Labels
bug
Something isn't working
Comments
Hi @invidian ! Thanks for reporting! |
Closed
iyehuda
added a commit
to iyehuda/kube-hunter
that referenced
this issue
Feb 20, 2020
Remove unnecessary imports from kube_hunter/__init__.py that cause hook registration before main file execution. This made the event loop handler indirectly configure the root logger, which in turn prevented the main file configuring it with user parameters. Fixes aquasecurity#292
iyehuda
pushed a commit
that referenced
this issue
Feb 25, 2020
py-go
pushed a commit
to py-go/kube-hunter
that referenced
this issue
Aug 29, 2021
Resolves: aquasecurity#292 Signed-off-by: Daniel Pacak <pacak.daniel@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened
It seems that since fe3dba9,
--log DEBUG
has no effect when runningkube-hunter
.Steps to reproduce:
docker run -it $(docker build . | tail -n 1 | cut -d" " -f3) --log DEBUG --pod
Reverting to fd4d79a restores proper logging behavior.
Expected behavior
Debug messages should show up when
--log DEBUG
is specified.The text was updated successfully, but these errors were encountered: