CPS-1031 - Getting issue details... STATUS

Introduction

To fulfill various usage needs it is important that all CPS applications can be configured when they are deployed without requiring any change in the application artifacts (docker images).

CPS applications configuration capabilities are provided by leveraging Spring Boot application properties provided by String Boot:

The properties that are available for configuration include both:

Custom CPS properties specific to the application
Spring Boot defined properties: https://docs.spring.io/spring-boot/docs/current/reference/html/application-properties.html#appendix.application-properties

Current Implementation (Jakarta)

CPS configuration properties are implemented at different level

1. Application Level

Following are the properties that should be defined at application level in the default application.yml file from the application repository:

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 CPS Core:

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:

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 should contain following properties:

All properties already defined in application application.yaml file but need to be changed (overridden) to provide another default value for Kubernetes deployment and runtime.
Any Spring Boot defined property that is not specified in application aplication.yml file but need to be specified (set) for Kubernetes deployment and runtime.

Any value property set in application application.yaml file and not re-defined in Helm profile is still loaded and kept unchanged. There is no need to duplicate the properties in Helm profile.