Closed ricardozanini closed 1 month ago
As depicted in https://sonataflow.org/serverlessworkflow/latest/use-cases/timeout-showcase-example.html#_architecture. there should be sinkbindings and triggers automatically created for the commute between workflow deployments and Dataindex/JobService
Particularly, the Sinkbindings and triggers are mandatory for Dataindex. for Jobservice, those objs need to be created depending on time-based events detected in workflow payload including timeout and sleep as described here
No response
I will look into this issue.
Started on a draft ADR
Just to have the link to the PR https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/467
Description
As depicted in https://sonataflow.org/serverlessworkflow/latest/use-cases/timeout-showcase-example.html#_architecture. there should be sinkbindings and triggers automatically created for the commute between workflow deployments and Dataindex/JobService
Particularly, the Sinkbindings and triggers are mandatory for Dataindex. for Jobservice, those objs need to be created depending on time-based events detected in workflow payload including timeout and sleep as described here
Implementation ideas
No response