| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Introduction
Currently, the default application configuration is present inside the docker images and it gets overridden when it is deployed using the helm. The issue with this approach is
...
To avoid it, we can keep only those properties in the OOM which needs to be changed based on deployment and provide an ability for overriding any property if required.
Possible Solutions
Final Approach: Approach 2 - Spring Profile
In any spring application, application properties can be provided in multiple ways, listed below in ascending order of priority.
- configured in thebapplicationthe application.yml in the resources folder
- configured in the application-<profile>.yml in the resources folder
- environment variables
- system property to JVM using -Dkey=value
...
In this approach, everything will be added in the environment variables which will make it difficult to identify in a running container which spring properties are overridden or added for application. We have to rely on configmap for a large set of environment variables which can make debugging inconvenient.
Approach 2 - Spring Profiles
| Anchor | ||||
|---|---|---|---|---|
|
Implementation: https://gerrit.onap.org/r/c/oom/+/120431/6
...