Following the discussion regarding circular dependencies on Apache KIE, we’ve migrated most of the Sonataflow packages to kie-tools (kogito-swf-builder image – renamed to sonataflow-builder-image, kogito-swf-devmode image – renamed to sonataflow-devmode-image, kogito-serverless-operator – renamed sonataflow-operator) [1]. They are currently building successfully on the kie-tools CI, but for the sonataflow-operator package we have never actually been able to test if it’s working correctly, either because there was an unreleased dependency (e.g. some snapshot build or image) at the time or simply because the e2e tests were not working on the original kogito-serverless-operator repository [2] and I lacked the proper knowledge to fix them.
My question is: Given that the sonataflow-operator and its dependencies are part of the Apache KIE 10 release, and considering that the kogito-serverless-operator repository is not listed as part of the release procedure [3], can we ensure that they are functioning as expected on kie-tools? The same question is valid for the kn-plugin-workflow, since it directly depends on the sonataflow-operator. [1] Packages on kie-tools: * sonataflow-operator: https://github.com/apache/incubator-kie-tools/tree/main/packages/sonataflow-operator * kn-plugin-workflow: https://github.com/apache/incubator-kie-tools/tree/main/packages/kn-plugin-workflow * sonataflow-builder-image: https://github.com/apache/incubator-kie-tools/tree/main/packages/sonataflow-builder-image * sonataflow-devmode-image: https://github.com/apache/incubator-kie-tools/tree/main/packages/sonataflow-devmode-image [2] kogito-serverless-operator repo: https://github.com/apache/incubator-kie-kogito-serverless-operator [3] Apache KIE 10 :: Release Procedure: https://docs.google.com/document/d/1t-08b970i9PMBy-TSM64x0RUH46pzwnIhEi-LVeL0lg/edit#heading=h.69qvogh2xqsq
