-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
False
-
-
False
-
-
Until https://issues.redhat.com/browse/SRVLOGIC-265 is implemented, we'll have to enable persistence for long-running workflows explicitly.
The solution requires extending the software template to enable persistence if selected by the user.
By enabling persistence to the workflow, the generated Sonataflow CR needs to be extended to contain the persistency attributes:
persistence: postgresql: secretRef: name: postgres-secrets userKey: POSTGRES_USER passwordKey: POSTGRES_PASSWORD serviceRef: name: postgres port: 5432 databaseName: sonataflow databaseSchema: callbackstatetimeouts
As specified in https://github.com/apache/incubator-kie-kogito-docs/pull/529/files#diff-36629490942c3ebc783d7315dafa3098c8196d8eb1d3f089598e35dbc66a1468R85
Additional changes are mentioned in this thread:
The acceptance criteria are:
- Having a software template that provides persistence capability to the created workflow
- is depended on by
-
FLPATH-1148 [Orchestrator] - workflow stuck in active state if workflow pod is deleted during workflow execution
- Closed