-
Notifications
You must be signed in to change notification settings - Fork 169
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
API OperatorFlagsMergeStrategy #2753
API OperatorFlagsMergeStrategy #2753
Conversation
260ca79
to
d245b08
Compare
Is there a reason we need a flag to merge these? IMO it should be default behavior to take whatever is present within the cluster document + whatever our defaults are, and merge them together. I don't really like adding additional series of flags because they're slowly getting out of control. Essentially my question would be: do we see ourselves ever using the "reset" functionality? If so, I understand the change, but I don't know when we'd ever purposefully use it. @hawkowl what are your thoughts? |
5c22b6c
to
614efbb
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.
Hi @SrinivasAtmakuri I have two questions and one humble request. Would you please cover this function with unit test to verify it is doing what is expected? Thank you
OperatorFlags: api.OperatorFlags{"aro.feature1.enabled": "false"}, | ||
}, | ||
}, | ||
body: []byte(`{"operatorflagsmergestrategy":"merge"}`), |
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.
@SrinivasAtmakuri would you please also add the reset strategy, to make it explicit and show that it works please?
5590835
to
21986e1
Compare
21986e1
to
d51901b
Compare
Adding more test cases and retesting the code. Will update once done. Thanks. |
deprioritized, marking this RP for closure. |
JIRA: https://issues.redhat.com/browse/ARO-1885
Which issue this PR addresses:
Fixes
What this PR does / why we need it:
Test plan for issue:
Is there any documentation that needs to be updated for this PR?