Add command line support for creating, building and running containerized integrations locally

[doru1004]

This patch adds command line options for creating, building and running local images.

A new local command, local create has been added to construct images.

The first image kind it can produce is a base image to be used as a starter for all integration images. Example of building a base image, the image will be saved under the default name of integration-base-image:

kamel local create --base-image --container-registry <registry-name>

The image can then be used as a base for creating and building integration images, the image will be used automatically every time an integration image is created. If a base image isn't available it will be created automatically. Example of building an integration image (without running it):

kamel local create --image <registry-name>/<my-image-name> -d <dep> -p <prop> --property-file <file> route1.java route2.yaml

The resulting image can then be run locally using the following invocation:

kamel local run --image <registry-name>/<my-image-name>

Local run has been enhanced with containerization capabilities i.e. it can now create, build and run container images locally. The following command containerizes and runs the integration (i.e. performs all previous steps automatically: base image creation and building, integration image creation and building, integration image running):

kamel local run --containerize --image <registry-name>/<my-image-name> -d <dep> -p <prop> --property-file <file> route1.java route2.yaml

Release Note

Added ability to package and run integrations locally or as container images

[nicolaferraro]

Thanks @doru1004 , it looks really promising. Just some comments to improve it.

[nicolaferraro]

Another issue is that kamel local create --base-image creates a maven structure in the current directory (pom.xml, src and target dirs).

[doru1004]

Another issue is that kamel local create --base-image creates a maven structure in the current directory (pom.xml, src and target dirs).

I fixed this. There were several other files and folders emitted and now no intermediate files/folders are emitted in the current directory.

[nicolaferraro]

Seems there is some other issue, I can't get kamel local run examples/routes.groovy to work (it does not print the periodic log message).

[doru1004]

Seems there is some other issue, I can't get kamel local run examples/routes.groovy to work (it does not print the periodic log message).

It looks like this has nothing to do with the latest changes, it probably has to do with redirecting the output of the command.

[doru1004]

Seems there is some other issue, I can't get kamel local run examples/routes.groovy to work (it does not print the periodic log message).

The -d camel-k:runtime-quarkus dependency needs to be added to the CLI then it all works. Perhaps we can add that dependency automatically every time.

[doru1004]

I have updated the patch to fix the reported problems. I have also changed the directories used inside the image to be the same ones used in the Kubernetes case! :)

[doru1004]

@nicolaferraro not sure why the knative test failed, it looks like there is a similar failure in master.

[doru1004]

Rebased on latest master.

[nicolaferraro]

Should you set the stdout and stderr here? It works but I see no logs

[doru1004]

Can definitely do that. Are there some guidelines as to how std out/err should be managed?

[doru1004]

I've added some simple redirection of stdout and stderr.

[doru1004]

I have also added the capability to include environment variables in modeline options:

test.yaml

# camel-k: property=camel.component.slack.webhookUrl=${SLACK_WEBHOOK}

When the modeline option is extracted, it will be added to the command line like this:

kamel local run --property=camel.component.slack.webhookUrl=hooks.slack.com/AAA/BBB/CCC

If the variable is not exported or has no value an error will be thrown.

[doru1004]

Rebased on latest master.