wmedvede commented on PR #372: URL: https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/372#issuecomment-1938230555
> > 4. **workflowtimeouts WF, with the configuration below has failed to deploy:** > > Here we would expect that the WF picks the platform persistence configuration and use it's own configured schema wf_timeouts. > > this is not the expected behavior as i understand it. in the below scenario, since that you're setting `workflow.spec.persistence`, the platform persistence settings are NOT used. whatever is set in the workflow will be used instead. if you wanted to use the platform persistence settings, then remove `persistence` entirely from the workflow `spec` below. > > > But the following error was produced at deployment. (Please @jordigilh correct me if the configuration is wrong. > > `The SonataFlow "workflowtimeouts" is invalid: spec.persistence.postgresql: Invalid value: 1: spec.persistence.postgresql in body should have at least 2 properties` > > ``` > > apiVersion: sonataflow.org/v1alpha08 > > kind: SonataFlow > > metadata: > > name: workflowtimeouts > > annotations: > > sonataflow.org/description: Workflow Timeouts Example k8s > > sonataflow.org/version: 0.0.1 > > spec: > > persistence: > > postgresql: > > serviceRef: > > databaseSchema: wf_timeouts > > ``` > > @wmedvede this is because `secretRef` is required here, as well as either the `serviceRef` or `jdbcUrl` field. Just add `secretRef` and the error should go away. I see, so in this case we are not inheriting but defining all the persistence for this particular workflow instead. My initial understanding was that is should be possible inherit persistence and only declare the WF schema to use if desired. -- 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]
