-
Feature
-
Resolution: Done
-
Critical
-
1.32.0
-
False
-
None
-
False
-
-
The operator must resync the workflow's custom properties ConfigMap <workflowname>-props when it changes. Usually, Kubernetes updates the application.properties mounted in the pod. The problem is that the application, when not in devmode, won't refresh it. It requires an application restart.
When a user changes the properties, the operator must rollout the application so that the properties will be refreshed.
Acceptance Criteria:
- When the user updates the properties ConfigMap and the SonataFlow instance has a prod profile, the associated Deployment starts new Pod(s) and, whenever they become ready, terminates the existing one(s)
- The operator annotates the Deployment with an annotation like operator.sonataflow.org/restartedAt with the timestamp of the new rollout, under the .spec.template.metadata.annotations path
- is documented by
-
SRVLOGIC-197 Design document
- Closed
- relates to
-
SRVLOGIC-195 Break the current operator's configuration into custom and managed properties
- Release Pending