You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data Index supports events for marking a workflow as deployed and undeployed. Since the operator controls this behavior cluster-wide, it makes sense for it to push events directly to DI once such events occur.
The event will be pushed to the Data Index in the SonataFlowPlatform definition. That can be either cluster-wide or namespace.
Operator to emit deploy and undeploy event following existing ProcessEventDefinition (I guess this can be one issue)
Runtime to remove current event publishing when the operator is there (we need to dicuss what happend when data index is embedded and there is not operator)
Data index to consume undeploy event (the current code for deploy event does not need to be touched)
Description
Data Index supports events for marking a workflow as
deployed
andundeployed
. Since the operator controls this behavior cluster-wide, it makes sense for it to push events directly to DI once such events occur.The event will be pushed to the Data Index in the
SonataFlowPlatform
definition. That can be either cluster-wide or namespace.For reference, this is the ProcessEventDefinition.
Implementation ideas
Every time a new workflow is deployed a new
Deploy
event will be emitted. We will add a finalizer to handleUndeploy
events to a given Data Index.The text was updated successfully, but these errors were encountered: