Page Comparison

...

• Application custom properties for any value that should not be hard-coded in the application code source. A default value is provided in the properties file. When deploying the application any user has the option to use the default value provided by the application or change the value to run with a different one.
• Spring Boot defined properties that need to be set for the application (either because Spring default value does not fit or is not set).

Detailed configuration:

• Kafka configuration at application level is a Plain Text basic configuration ready to be used and tested easily on a local dev environment.

For example , see properties file for CPS applicationCore:

• https://github.com/onap/cps/blob/jakarta/cps-application/src/main/resources/application.yml

2. Helm Chart Level

When CPS applications are deployed in a Kubernetes environment, they are configured to run with a specific helm Spring profile specified by `SPRING_PROFILES_ACTIVE` environment variable. For example, see CPS Core:

• https://github.com/onap/oom/blob/jakarta/kubernetes/cps/components/cps-core/templates/deployment.yaml#L92
• https://github.com/onap/oom/blob/jakarta/kubernetes/cps/components/cps-core/values.yaml#L177

Then, OOM chart application-helm.yml is mounted in the application container to provide`helm` profile configuration values. For example see CPS Core:

• https://github.com/onap/oom/blob/jakarta/kubernetes/cps/components/cps-core/templates/deployment.yaml#L102

OOM chart application-helm.yml contains following properties:

• ...

For example see CPS Core:

• https://github.com/onap/oom/blob/jakarta/kubernetes/cps/components/cps-core/resources/config/application-helm.yml

3. Helm Values Level

...