Cannot use custom components easily

[kjq]

Bug description

Basically, we have custom components that we use today in Camel (and through jBang). There are just regular components not Quarkus extensions.

They are added using the Kamel CLI as "dependencies" to the spec.

When deploying a route it appears to require that the component exists in the catalog or it cannot find it and errors out fast.

There is a whole conversation around this on Zulip @ #camel-k > How to use custom Components and Maven

As a workaround, this seems to work patching the catalog with the component

kubectl patch camelcatalog camel-catalog-quarkus-3.15.3 -n camel --type=merge -p '{
  "spec": {
    "artifacts": {
      "acme-prompt": {
        "groupId": "io.acme",
        "artifactId": "acme-workflow-components-intellect",
        "version": "1.0.0-SNAPSHOT",
        "schemes": [
          {
            "consumer": {},
            "http": false,
            "id": "acme-prompt",
            "passive": false,
            "producer": {}
          }
        ]
      }
    }
  }
}'

Per @squakez

let us know how it goes. And please, log an issue to track the request to include the feature to skip the component validation: this one could easily go in next release

Camel K or runtime version

2.10.1

[squakez]

Thanks for providing a workaround while we work on #6254

We can develop an immediate patch to let the user provide the component as a dependency and skipping the catalog validation as we've discussed. This issue is a tracker for that work that we can include in next release.