Closed jaellio closed 1 year ago
i'm surprised we don't have the linter enabled to ensure errors are checked. We should check and do something with those errors most likely
In general yes, but for a backport, we should probably persist existing behavior right?
In general yes, but for a backport, we should probably persist existing behavior right?
I'll just point out this is more than a backport if its making it into main
In general yes, but for a backport, we should probably persist existing behavior right?
I'll just point out this is more than a backport if its making it into main
Oh I misread which PR this is. That's a fair point...in that case, I don't have a strong preference for which direction we go this PR
In general yes, but for a backport, we should probably persist existing behavior right?
I'll just point out this is more than a backport if its making it into main
Agree, it isn't much code to change to add the error handling. I've updated the PR to include these changes.
Description: Fixes lint error introduced in #5283
When upgrading helm to 3.11.1, the k8.io client-go package was also updated to v0.26.3. In v0.26 the API for
AddEventHandler
was updated to return an error and registration handle to enable individual handler cancelation.Please answer the following questions with yes/no.
Does this change contain code from or inspired by another project? No
Is this a breaking change? No
Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)? No