This epic is all about defining how workflow which is being developed in a Git repository will find itself deployed to a k8s cluster, and its lifecycle (e.g. upgrades and deletion).

Some of the workflows will contain only the workflow definition, openapi specs, input/output schema, and configuration files.

Other workflows may contain also custom Java code.

Acceptance criteria:

• A recommended directory structure for the resources to be deployed on SonataFlow operator
  • A tool to produce the above (e.g. an extension to maven quarkus-kubernetes plugin. The output should look similar to https://github.com/rgolangh/sonataflow-argocd-app/tree/main 
  • This should include support in workflow definition, specs and, input/output schema representation as SonataFlow CR, secrets, configmaps
• For a custom code, add an attribute in the SonataFlow CR to the flowContainer image
  • Provide a method to build the custom code image and deploy it to a registry to make it available for the workflow deployment
    • Options are: BuildConfig
• Define a CI process to include the following steps:
  • Building an image (build)
  • Verify the quality of a workflow (test)
  • Push to a registry (release)
  • Update manifests to the built image digest
• A recommended CD procedure to deploy the generated resources above to k8s cluster (e.g. GitOps approach)