-
Epic
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
RFE A user of IDP config should be able to apply a new Oauth config and not lose the existing one(s)
-
False
-
None
-
False
-
To Do
-
0
-
0%
Epic Goal
- A user of IDP config should be able to apply a new Oauth config to a managed cluster, and if that managed cluster already has some Oauth defined, they would not lose the existing Oauth(s), we would just add to it.
- In short: merge new Oauth instead of overwrite all of them
Why is this important?
- Currently we document this limitation: https://identitatem.github.io/idp-mgmt-docs/quick_start.html#getting-started
- A user may not notice this (even thought we mark it as IMPORTANT)
- .
Scenarios
- A user may want to configure existing managed clusters that use existing OAuth configs.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- Import existing clusters that have defined Oauth
- Check against managed OpenShift ROSA, in which a user can define a 'quick access' `cluster-admin` Oauth
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions:
- What's the best way to expose this configuration option to the user?
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 - Downstream documentation merged: <link to meaningful PR>
