NONRTRIC - PMS Fix dynamic configuration 45/7545/3
authorPatrikBuhr <patrik.buhr@est.tech>
Thu, 9 Dec 2021 13:16:01 +0000 (14:16 +0100)
committerPatrikBuhr <patrik.buhr@est.tech>
Wed, 12 Jan 2022 13:43:02 +0000 (14:43 +0100)
commit4c590d97d5cc689e8e1f338bd740f8e585a4e0ec
tree352571720b6e7ca9ff7d9c73fa04a4b8afb95d65
parent998f077bd3228cf136283a05cc2350d3f6cb3788
NONRTRIC - PMS Fix dynamic configuration

The problem was that the config cannot be updated via REST if the file is controlled by a configmap.
The configmap for PMS application can only be used for initial configuration after this change.

The file is moved from
/opt/app/policy-agent/data/application_configuration.json -> /var/policy-management-service/application_configuration.json

/var/policy-management-service/ is mapped to a persistent volume claim.

Config map which now is only initial (installation) data is mapped to:
/etc/app/policy-management-service/initialdata

An init container copies the initial configuration file /etc/app/policy-management-service/initialdata/application_configuration.json to /var/policy-management-service/
unless it is already there.

Signed-off-by: PatrikBuhr <patrik.buhr@est.tech>
Issue-ID: NONRTRIC-689
Change-Id: I79be05bbc4d18ad1914efc3cbcdf932ede71718d
nonrtric/RECIPE_EXAMPLE/example_recipe.yaml
nonrtric/helm/nonrtric/templates/pv1.yaml
nonrtric/helm/nonrtric/templates/pv2.yaml
nonrtric/helm/nonrtric/values.yaml
nonrtric/helm/policymanagementservice/resources/config/application.yaml
nonrtric/helm/policymanagementservice/templates/statefulset.yaml