ricardozanini commented on issue #436: URL: https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/436#issuecomment-2045862615
I'll add a few implementation ideas here so others can chime in. If needed, I can create a design doc. So I think we can have a `.spec.properties.flow` within the `SonataFlowPlatform` interface. This attribute can be a map of a complex object derived from the [Kubernetes Env Var](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#envvar-v1-core) API, meaning that the propagated properties can be defined directly to the CR. Example: ```yaml apiVersion: sonataflow.org/v1alpha08 kind: SonataFlowPlatform metadata: name: sonataflow-platform spec: properties: flow: - name: quarkus.http.auth.permission value: myValueForTheProperty - name: quarkus.http.auth.policy valueFrom: secretKeyRef: my-secret keyName: my-policy optional: false - name: quarkus.other.property valueFrom: configMapRef: my-config-map keyName: my-property optional: false ``` So one can either set the value directly, from a secret or configMap. We use `.spec.properties.flow` to have some room to add properties for the Data Index, or any other supporting service or future actor in the platform. ## Cluster Platform In the cluster platform, we are going to set the `.spec.capabilities` to `properties.flow` by default. So one can set to an empty value if the cluster platform does not propagate the properties to the whole cluster. @masayag @gabriel-farache @wmedvede @jakubschwan please let me know what you think. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
