-
Task
-
Resolution: Done
-
Major
-
None
-
2.5 GA
-
None
-
2
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
Context
We use rolling updates in porta to enable/disable features for container builds
But on-premises builds are using volume mounts to set those values. Which sometimes lead in desynchronization and mistakes. See https://github.com/3scale/3scale-operator/pull/117#issuecomment-478922952
This is the System issue. The corresponding OSE Templates issue is THREESCALE-2649.
Goal
- remove the templates volume mounts, having one default from the code. Less maintenance, one source of truth
- defaults can be merged with existing extras configs.
- document how to enable/disable certain features on-premises
Dev notes
The ideal solution would be:
- defaults are read from the config/*.yml
- custom are read from /opt/system/extra-configs/*.yml and overrides to the defaults.
- for rolling_updates.yml, they will be merged with the defaults
- is blocked by
-
THREESCALE-2649 Use code rolling updates instead of templates volume mounts
-
- Closed
-
- is duplicated by
-
THREESCALE-3553 Automate changes in amp.yml
-
- Closed
-