Here some documentation related to how Camel K manages dependencies:
https://camel.apache.org/camel-k/1.7.x/configuration/dependencies.html
The most important managed component dependencies are the ones discovered
in the route definition. Those are always picked and included in the
integration. Th
So, If I try to use some dependency like camel:rest it will not be
resolved even if I put it on a modeline (and submit the yaml to the
k8s API) ?
On Tue, Dec 21, 2021 at 6:24 AM Pasquale Congiusti
wrote:
>
> Hello Roberto,
> the cron dependency is likely autodiscovered from your component route
>
Hello Roberto,
the cron dependency is likely autodiscovered from your component route
definition (ie, cron:xyz), whilst the microprofile is instead defined by
the prometheus trait, so, although you don't define it explicitly, then,
the dependency is added during the application build.
Regards,
Pas
I'm launching camel-k integrations via kubernetes API.
I just create an "Integration" resource definition in JSON and submit it.
Recently I was trying to create integrations with dependencies like
"camel:cron" and "camel:microprofile-metrics" but WITHOUT defining
them in the "dependencies" field.
