Chapter 6. Configuring workflow services

Procedure

1. Open your terminal and access the OpenShift Serverless Logic project. Ensure that you are working within the correct project, namespace, where your workflow service is deployed.

   $ oc project <your-project-name>

2. Identify the name of the workflow you want to configure.

   For example, if your workflow is named greeting, the user-defined properties are stored in a ConfigMap named greeting-props.

3. Edit the workflow ConfigMap by executing the following example command:

   $ oc edit configmap greeting-props

   Replace greeting with the actual name of your workflow.

4. Modify the application.properties section.

   Locate the data section and update the application.properties field with your desired configuration.

   Example of ConfigMap

   apiVersion: v1
   kind: ConfigMap
   metadata:
     labels:
       app: greeting
     name: greeting-props
     namespace: default
   data:
     application.properties: |
       my.properties.key = any-value
     ...

5. After updating the properties, save the file and exit the editor. The updated configuration will be applied automatically.

Procedure

1. Locate the SonataFlowPlatform resource in the same namespace as your workflow services.

   This is where you will define global managed properties.

2. Open the SonataFlowPlatform resource in your default editor by executing the following command:

   $ oc edit sonataflowplatform sonataflow-platform-example

3. Define custom global managed properties.

   In the editor, navigate to the spec.properties.flow section and define your desired properties as shown in the following example:

   Example of a SonataFlowPlatform with flow properties

   apiVersion: sonataflow.org/v1alpha08
   kind: SonataFlowPlatform
   metadata:
     name: sonataflow-platform-example
   spec:
       properties:
           flow: 

   1

   
            - name: quarkus.log.category 

   2

   
              value: INFO 

   3

   1

   Attribute to define a list of custom global managed properties.

   2

   The property key.

   3

   The property value to apply globally.

   This configuration adds the quarkus.log.category=INFO property to the managed properties of every workflow service in the namespace.

4. Optional: Use external ConfigMaps or Secrets.

   You can also reference values from existing ConfigMap or Secret resources using the valueFrom attribute as shown in the following example:

   Example of a SonataFlowPlatform properties from ConfigMap and Secret

   apiVersion: sonataflow.org/v1alpha08
   kind: SonataFlowPlatform
   metadata:
     name: sonataflow-platform-example
   spec:
       properties:
           flow:
            - name: my.petstore.auth.token
              valueFrom: 

   1

   
                   secretKeyRef: petstore-credentials 

   2

   
                       keyName: AUTH_TOKEN
            - name: my.petstore.url
              valueFrom:
                   configMapRef: petstore-props 

   3

   
                       keyName: PETSTORE_URL

   1

   The valueFrom attribute is derived from the Kubernetes EnvVar API and works similarly to how environment variables reference external sources.

   2

   valueFrom.secretKeyRef pulls the value from a key named AUTH_TOKEN in the petstore-credentials secret.

   3

   valueFrom.configMapRef pulls the value from a key named PETSTORE_URL in the petstore-props ConfigMap.