Currently, the operator will create a configmap name ${workflwo_name}-props if it doesn't exist. The configmap contains the properties used by the quarkus application to configure the workflow application.

In case the properties configmap was created by the user, the operator will merge the system configuration into that configmap and will update the owner reference of that config map to be the SonataFlow CR to which it refers. 

—

The purpose of this epic is to allow a workflow to be configured by providing its properties from several sources (user, system, and managed ones).

When the user's created resources, such as the properties configmap, are managed by GitOps and ArgoCD, any change by the operator to the configamp will cause the resource to be out of sync.

In addition, certain configuration values are determined by the operator, based on the workflow profile and target deployment.

This epic suggests the user will be able to maintain the workflow configuration on its codebase, detached from the deployed resource while enabling the operator to enrich the configuration based on the target cluster, namespace/platform, and workflow profile without having an impact on the user's configuration.