EPIC - Support deploy/undeploy SonataFlow Flow definitions events on Data Index

[ricardozanini]

Issues in this epic:

• SonataFlow Operator should emit deploy and undeploy events when Data Index is available in a given namespace incubator-kie-kogito-serverless-operator#458
• (TBD) 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)
• Allow Data index to consume undeploy events incubator-kie-kogito-apps#2050

Originally posted by @fjtirado in apache/incubator-kie-kogito-serverless-operator#458 (comment)

[ricardozanini]

@fjtirado @nmirasch can you please open the mentioned issues? 🙏

[nmirasch]

@ricardozanini here it is the dataindex related one apache/incubator-kie-kogito-apps#2050

[fjtirado]

After some discussion, we agree that the simplest approach is to add a new event topic (to not interfere with audit component), which events will contain the id and version of the workflow plus the "deployment status".
Data Index will consume that information and merge it into the process definition existing structure (therefore the result will be that the existing process definition in data index will include the deployment status as result of the queries)
With this approach, we do not need any issue for runtime.
In my original comment, I forgot to mention that we need an issue for tooling (for dealing with the new "deployment status" field)

[ricardozanini]

@paulovmr @caponetto can you assess?

In my original comment, I forgot to mention that we need an issue for tooling (for dealing with the new "deployment status" field)

We can add a task in this EPIC.

[caponetto]

IIUC, on the tooling side, we can filter out data by the new deployment status field on the queries. This way, we maintain the behavior of showing only those deployments that are indeed alive.