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. I leted this dependencies inside the
source code via "modeline", and for my amazement camel-k operator has
built the kit correctly.

But the case is that the "Integration" resource (obtained via kubectl
get intergration <my-integraton> -o yaml) doesn't describe the
dependencies.

Can I assume this is the expected behavior? That the operator will
"parse" the source and use the correct dependencies even if the source
Integration resource hasn't contracted them?

Reply via email to