-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
✨ clusterctl: Allow user to suppress API warnings #11149
✨ clusterctl: Allow user to suppress API warnings #11149
Conversation
/cc @sbueringer |
664b3f2
to
142cbb2
Compare
I also have a commit that uses this to hide API warnings in the |
/area clusterctl |
Thx! /lgtm |
LGTM label has been added. Git tree hash: f96dd35df5dc79f2bcc688d3e838b5c1b9f7fa59
|
Maybe we should only hide specific warnings, but no strong opinion (+ let's discuss this on the next PR) |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 this PR does / why we need it:
Allows the clusterctl user to configure the API client warning handler.
The warning handler is configured by the Proxy. If a user only wants to configure the warning handler, we should not require them to implement their own Proxy. This PR, therefore, exports our Proxy constructor, and adds an option that allows the user to construct a Proxy with their own warning handler.
The PR does not change the existing warning handling behavior. As before, the default warning handler is provided by the controller-runtime client. Its default warning warning handler has not changed.
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 #10932