-
Notifications
You must be signed in to change notification settings - Fork 170
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
[ARO-1885] Implement OperatorFlagsMergeStrategy #3911
base: master
Are you sure you want to change the base?
Conversation
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
tests := []struct { | ||
name string | ||
oc *api.OpenShiftCluster | ||
wantOc *api.OpenShiftCluster |
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.
The variable wantOc
is declared, but its usage is not shown anywhere.
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.
I think we shouldn't change the struct, but we should change only API because OperatorFlagsMergeStrategy is something only used for this API ad-hoc, and essentially not an attribute of the OpenShiftCluster struct.
Which issue this PR addresses:
Fixes https://issues.redhat.com/browse/ARO-1885
What this PR does / why we need it:
Allows us to 'reset' feature flags to their defaults by providing ones that we wish to layer on top of said defaults.
Broken out of #3571 because I needed it for some tests. Based off work by @SrinivasAtmakuri in another PR.
Test plan for issue:
Unit tests
Is there any documentation that needs to be updated for this PR?
SOPs for operator flag working might be needed?
How do you know this will function as expected in production?
Unit tests, plus it won't do anything in production unless we make it do so