-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
None
-
False
-
-
Our fork needs to have a minimal set of changes compared to the upstream repository. Ideally, we can keep these changes in a separate file so we don't experience git conflicts.
Acceptance Criteria:
- it's possible to switch between upstream and downstream files when building manifests (e.g. using env variables VERSIONS_FILE, VALUES_FILE, or Makefile.overrides)
- set product operator version to 3.0.0
- Setup a sync job with upstream (e.g. for each commit? daily?)
- new files must not break updates done by Automator
- custom values.yaml for CSV generation
- cpaas is configured to use generated downstream manifests from the fork repo
- blocks
-
OSSM-5941 Add product versions.yaml and values.yaml to operator repo fork
- Closed
- mentioned on