-
Epic
-
Resolution: Unresolved
-
Critical
-
ACM 2.12.0, MCE 2.7.0
-
Installer Resolve conflicts in the AddOnDeploymentConfig API between default values and user inputs
-
False
-
None
-
False
-
Green
-
To Do
-
-
50% To Do, 17% In Progress, 33% Done
Epic Goal
There are some resources, like ClusterManagementAddOn and AddOnDeploymentConfig, that are created by installer and users are allowed to customize the resources spec for advanced configuration. Here comes the conflict:
- the installer always tries to keep the default value by force patching the filed managed by itself;
- the user may need to update the filed managed by installer;
The situation becomes even worse in the upgrading case, the installer may rollback the user configuration which works well in the previous release and result in unexpected issues.
The goal of this epic is to figure out an appropriate way to handle the potential configuration conflicts between the default value and user inputs.
Why is this important?
...
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.
- relates to
-
ACM-11694 [RFE] Prevent the resource from being changed back after the user changes
-
- New
-
