We aim for a better experience for our end users towards trying the Kogito Workflow engine.

Today, to deploy a simple workflow in an OpenShift cluster, a user has to create a local maven project, add the workflow definition file to the resources folder and push the entire project with the kogito deploy <folder> command.

To deliver a better experience, a user could create their own workflow definition via the VSCode plugin and push the file with kogito deploy <file.sw.json|yaml|yml.

To cover this feature, we would need a Quarkus extension for kogito workflows or at least a kogito-serverless-workflow-bom module with the dependencies needed for a Kogito Workflow project. Our s2i builder image would then use this BOM to generate the maven project, compile the jar file, build, and push the image to the internal registry.

We would need:

1. Create the BOM module
2. Adjust the s2i script in the kogito-images project to recognize an SW file and build it accordingly.

One side note: A user could push multiple workflow definition files with the same command (with subflows, for example). So the command kogito deploy <folder> should be considered as well.