Camel JBang

When using JBang then JBang stores state in ~/.jbang directory. This is also the location where JBang stores downloaded JARs.

So if you find problems with JBang using what is seems like an outdated JAR, then you can try to delete this directory, or parts of it.

You can specify which Camel version to run as shown:

You can run more than 1 file, for example to run two YAML files you can do:

You can also mix different DSLs such as yaml and Java:

You can also use wildcards (i.e. *) to match multiple files, such as running all the yaml files:

Or you can run all files starting with foo*

You can enable live reload of the route(s) when the source file is updated (saved), using the --reload options as shown:

Then while the Camel application is running, you can update the YAML route and update when saving.

You can run a route that is hosted on GitHub using Camels github resource loader.

For example to run one of the Camel K examples you can do:

You can also use Camel JBang to try local Kamelets, without the need to publish them on Github or package them in a jar.

You can use the CLI to search for kamelets, components, languages and miscellaneous components (others). Running the following command will present a list of items that can be searched:

For example, to search for kamelets named jms, you can use:

To list all the kamelets, just run the command without any search term:

The same behavior also works for all the other search commands. The table below lists all search commands available at the moment:

The init sub-command can be used to simplify creating Kamelets. Through this command, it is possible to create new Kamelets through pre-configured templates. It works in two steps: first it is necessary to bootstrap the Kamelet by creating a properties file with the parameters necessary to create the Kamelet. Once the properties file is correctly set, then it is possible to create a pre-filled Kamelet by processing that properties file.

To bootstrap the Kamelet run:

This will create a sub-directory called work in the current directory with a properties file named init-template.properties inside it.

The keys of the properties file are commented with the details about what need to be filled in order to generate the Kamelet. If a value is missing, it will be ignored when generating the Kamelet and will need to be filled in manually later.

After you have filled the values, you can generate the Kamelet using:

Running this command will create a new file in the work directory. The name of the generated file is determined by the kameletMetadataName property in the properties file. As such, parsing the default properties file would generate a file named my-sample-sink.kamelet.yaml in the directory.

After the file is generated, it may still need to require final adjustments, such as correctly setting the name, the icon and other requirements for official Kamelets. Please consult the Kamelet development documentation for updated details.

The init sub-command can also be used to simplify creating Kamelets bindings. Through this command, it is possible to create new bindings through pre-configured templates. Use the --kamelet option (you can list the available ones using the search command) to set the Kamelet to generate the binding for.

To execute this feature run:

This will create a new sample YAML binding file that can be modified and used in Camel K.

You can also generate bindings that can be run by CamelJBang or Camel Core, but setting the --project option: