If you run Axon Ivy Engine in a container environment such as Kubernetes, you may use ConfigMaps. With the help of ConfigMaps you can provide configuration files like the ivy.yaml
in the Axon Ivy Engine Container. Those files are read-only. This is good, you may want to have control only in your Helm Charts about those files and have the same state for all your deployments - provisioning a new pod.
But until now this was not very good for the Engine Cockpit. Many of the features in the Engine Cockpit are writing the changes directly into the ivy.yaml
file. This prevents you from changing any configuration of a running pod. It will fail if you want to change a setting and try how it behaves.
To overcome this issue we will copy the configuration to a writeable directory. The Axon Ivy Engine will now only work with the copied version. If you make any changes, it works. But be aware, that you manually need to transfer the changes into your ivy.yaml
of your Helm Chart.
To find it out, if you run with a copied ivy.yaml
, you can check the Engine Cockpit 'Config File Editor'. This behavior has been implemented for all files, which we expected runtime changes:
- ivy.yaml
- app.yaml
- ivy.cache.properties
- log4j2.xml
- application configuration files
- branding
For Leading Edge 11.3.0 also truststore and keystore are handled this way.
This feature comes with Axon Ivy 11.3 and will be backported to Axon Ivy 10.0.19.