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 <[email protected]> wrote: > > 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, > Pasquale. > > On Mon, Dec 20, 2021 at 5:39 PM Roberto Camelk <[email protected]> > wrote: > > > 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? > >
