Camel capability is unstable (0.0.9-SNAPSHOT)

[actraiser2]

Hi,

When i've regenerated the images 0.0.9-SNAPSHOT associated the router instance and camel capability, unfortunately the log console has started to generate errors, and the Camel capability pod does directly not start

Below you can see the log dumped by the camel capability pod

These errors were not ocurring a 1 week ago with the same image 0.0.9-SNAPSHOT. Is it due to some breaking changes in the code?

Regards

[orpiske]

That is because we have added a new feature called data store. Earlier you had to copy the files to the Camel Integration Capability pod. However, now Wanaku comes with a builtin data storage that the capabilities can use to download the files.

Essentially, now you just need to add the files to the router's data store:

wanaku data-store add ...

Then, adjust the CIC container to use those by passing a reference to them --routes-ref datastore://filename.yaml

I haven't documented it yet, but you can look at the --help for the following commands:

• wanaku auth for the login parts
• wanaku data-store to manage the data store

And do the same on the CIC, as the parameters for the routes, rules and dependencies have changed to use a reference to the data store address of the files (ie: datastore://filename)

[orpiske]

The idea here is to make it easier to use the CIC. With the data store you don't need a side car container to download the files or complicated scripts to copy them to the pod once it is running.

Acquiring the resources it is just a part of the registration process between the capabilities and the router.

[actraiser2]

Hi @orpiske ,

Understood.

I think it could be practical to maintain both methods. So I can store the files in a git repository (gitops paradigm), and by the init container they are downloaded and enabled in a configurable path

Ok, i'm testing the new procedure, i've run into with a pair of issues:

I've uploaded the rules file, the routes file and the dependency of camel-kafka to the datasource of the router instance using the wanaku router UI

First issue:
Camel capability instance loads all of them, but ultimately it breaks with a exception with little information of the reason of the failure

Second issue:

If i configure several dependencies (for example, camel-oauth and camel-kafka), it appears another type of error

The parameter --dependencies is configured as a comma-separated list, such as:
datasource://camel-kafka,datasource://camel-oauth

Regards

[orpiske]

Here's one I am happier with: wanaku-ai/camel-integration-capability#27

[actraiser2]

It sounds great !!!!!!!.

Is it integrated in the image camel-integration-capability:0.0.9-SNAPSHOT for a try?

[orpiske]

There will be a new beta release in about 1-2 hours

[orpiske]

It's out now.

[actraiser2]

Thank you

I confirm you that pointing to the schema: file://....., the files are loaded correctly

[actraiser2]

Hi @orpiske ,

Any hint why is failing the Camel capability while loading the rules, routes and dependency files from the datasource of the router instance?

I paste again the stacktrace

If you need more information, you don't hesitate to request it

Kind Regards

[actraiser2]

The files were loaded from the UI, through the button 'add datasurce'

[orpiske]

So, the problem is that your are publishing the dependency itself in the data store. You should publish only a dependencies.txt file with a list of dependencies. For instance, something like this:

org.apache.camel:camel-http:4.14.2,org.apache.camel:camel-jackson:4.14.2

The Camel Integration Capability then consumes this file and downloads everything listed in there.

[actraiser2]

Hi @orpiske

You are right. Uploading only the file (which lists all the dependencies) to the datasource, the camel capability instance starts successfully, loading every route correctly.

Only a issue that i've detected. The name of the route file you load in the datasource has to have extension .yaml. If you omit the extension, the route loader of the camel capability instance crashes

The rule file doesn't have this problem