-
Notifications
You must be signed in to change notification settings - Fork 431
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
fix log flags #4301
fix log flags #4301
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4301 +/- ##
=======================================
Coverage 59.73% 59.73%
=======================================
Files 192 192
Lines 19303 19303
=======================================
Hits 11531 11531
Misses 7142 7142
Partials 630 630 ☔ View full report in Codecov by Sentry. |
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.
/lgtm
/approve
good catch!
LGTM label has been added. Git tree hash: 3ac6fe0cfdcf66f9f7f863b538aca1ac78a20db3
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR fixes a regression by #4274 where the command line flag configuration from main.go was no longer matching the logging implementation being set up, so flags like
-v
were no longer having any effect. This PR removes thetextlogger.Config
from main.go and instead sets up command line flags withklog.InitFlags
.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs:
Release note:
^ this bug has never affected any users of published releases.