-
Task
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
-
RHOAM Sprint 60, RHOAM Sprint 61, RHOAM Sprint 62, RHOAM Sprint 63
WHY
We want to allow users to make changes to their OAS and have those changes be reflected in the Product CR.
WHAT
Add support to the operator to detect when the source OAS for an OpenAPI CR has changed and apply those changes to an existing Product CR. Now that users can fully define a Product CR using OAS extensions, we can designate the OAS to be the single source of truth. Therefore any changes to the OAS source will be passed down to the Product CR but any changes on the Product CR itself will be reverted by the operator.
NOTE: The OpenAPI CR is the source of truth for any security related Product fields (which is just the `.spec.deployment` block on the Product CR) while the OAS is the source of truth for all other Product fields. Therefore the operator will need to watch for changes on both the OpenAPI CR and the OAS source (either secretRef or urlRef).
HOW
For secretRef OpenAPI CRs, the operator can just watch the OAS secret to monitor changes. For urlRef OpenAPI CRs, the operator will need to use a poll to periodically check the OAS source for changes.
DONE
- The operator recognizes when the OAS source or OpenAPI CR has changed and updates the Product CR accordingly
- links to
- mentioned on