Currently, the configuration is backed into the image. This requires having multiple ECR repositories per config. Config could be supplied externally and there should be only one the image per version
Feature
Find a way to supply the config externally to the image and change the image-building process to support this. Any deployment worklows based needs to be changed, too.
Proposed Solution [Optional]
Solution Ideas:
Load config from an external path that resides on a mounted volume
Require full config there, or
Require just override from a builtin default (this can be useful, but dangerous)
Require just override from a builtin default, but make sure that built-in misses some fields and thus fails if config is not provided
dk1844
commented
5 months ago
Background
Currently, the configuration is backed into the image. This requires having multiple ECR repositories per config. Config could be supplied externally and there should be only one the image per version
Feature
Find a way to supply the config externally to the image and change the image-building process to support this. Any deployment worklows based needs to be changed, too.
Proposed Solution [Optional]
Solution Ideas: Load config from an external path that resides on a mounted volume