It looks like some of the persistence related configurations are applied to the WF producing an error. Note that a WF with the dev profile shouldn't take any persistence configuration from the SFP.
To reproduce:
1) deploy a SFP with persistence configured in a namespace my-namespace
2) deploy a WF with the dev profile in my-namespace
3) see the logs for the WF's Pod for the errors.
Describe the bug
When we deploy a workflow with the dev profile in a namespace that already has deployed a SPF with persistence configured, e.g.:
It looks like some of the persistence related configurations are applied to the WF producing an error. Note that a WF with the dev profile shouldn't take any persistence configuration from the SFP.
To reproduce:
1) deploy a SFP with persistence configured in a namespace my-namespace 2) deploy a WF with the dev profile in my-namespace 3) see the logs for the WF's Pod for the errors.
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Golang version
No response
Operator-sdk version
No response
SonataFlow Operator version or git rev
No response
Additional information
No response