Today the only supported way to build a new Kogito Service from source is relying on Git URLs since the standard s2i way is to pull from a remote git repo, hence the operator was implemented this way.

The idea is to implement something similar to oc new-build . where the oc client upload the contents of a local directory to the OpenShift cluster and then start a new build.

Suggested command:

kogito deploy-service NAME PATH

Where PATH can be just a period representing the local path or a full path like /home/arnold/my-kogito-project

This way users can upload DMN or BPMN files directly to the cluster and the CLI will take care of uploading those resources and build a new microservice for it.

Dev list discussion regarding this implementation:
https://groups.google.com/forum/?#!msg/kogito-development/9JiLwZwfb94/Zx7m_UMtBwAJ

That's what this feature should implement:

Let's put this in a scenario:

1. You do not have a service deployed and you want to give it a go to a BPMN process you just built. You do:

• kogito deploy-service my-service /path/to/bpmn/domain/classes/files

2. Your service is up and running.

3. You made changes to your files and want to see them again in the cluster. You repeat the command:

• kogito deploy-service my-service /path/to/bpmn/domain/classes/files