-
Notifications
You must be signed in to change notification settings - Fork 394
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
🌱 crdcleanup: strongly type enqueue params #2573
🌱 crdcleanup: strongly type enqueue params #2573
Conversation
Signed-off-by: Andy Goldstein <[email protected]>
137fe6e
to
2b25d26
Compare
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
@@ -80,33 +80,29 @@ func NewController( | |||
|
|||
crdInformer.Informer().AddEventHandler(cache.FilteringResourceEventHandler{ | |||
FilterFunc: func(obj interface{}) bool { | |||
crd, ok := obj.(*apiextensionsv1.CustomResourceDefinition) |
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.
Technically this is a regression in behavior but I think in practice it's the more correct thing to do anyway?
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.
Yes, but it's better to panic to indicate programmer error I'd say.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: stevekuznetsov, vincepri 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 |
Summary
Strongly type the params used in our enqueue functions to avoid accidentally enqueueing the wrong kind of object.
Related issue(s)
Fixes #