We must be sure that when the jobs-service is used in the current sonataflow_platform, the  kogito-addons-quarkus-jobs-knative-eventing addon is properly incorporated when the workflow image is produced.

However, we must evaluate the different alternatives.

1) the kogito-addons-quarkus-jobs-knative-eventing addon is added by default in the 
kogito-swf-builder image.
 

Pros: no need to code anything, the sw-builder image always contains the addon

Cons: workflows generated with this alternative, if a timer is present, they will always try to send events to the jobs service, which in production enviroments makes sense since the jobs service is a standalone service. (when the collocated jobs service is in palace we migth need to incorporate a different addon, but this is the future...)

 
2) a smarter adding is done, for example, at the time the platform is being deployed the operator might detect if the jobs service is enabled, and in that case, the extension can be dynamically added to the platform being created.

Pros: the operator has the control

Cons: more code to maintain. And also, workflows that were build externally must have been build already with the addon present, so here the operator can help in that regard.
 
 
3) any other "smart" alternative.
 
 

Note:  the Dev profile is a different scenario that is already covered, and thus, not affected by this change. I that case we are already incorporating the required addons, etc.