squakez commented on issue #6306: URL: https://github.com/apache/camel-k/issues/6306#issuecomment-3347376331
> It solve the issue even if it wasn't my initial goal (See the original discution on zuplin). I wanted at first to dynamically load Kamelet at runtime. Do you know if it's possible with spec.traits.kamelets.mountpoint ? If you prefer i open another discussion for that i close this one Not sure. As explained in the [Kamelets architecture documentation](https://camel.apache.org/camel-k/next/architecture/kamelets.html), the operator is in charge to get the Kamelet specification required by your Integration (by scanning the source code) and mount the file in that mountpoint which is used at runtime to load Kamelets from. Now, your problem is that you don't know at deployment time which Kamelets are required because that is a runtime information and you're already late. The only possibility is to either preemptively load all potential Kamelets (at this stage, better via a dependency jar containing all of them), I cannot really think how else you can get this runtime information before the runtime execute. Something else could be to get the information from the Integration property, for example, hooking it up a [custom pipeline task](https://camel.apache.org/camel-k/next/pipeline/pipeline.html#add-custom-tasks). However I think it's really a challenging situation bec ause the separation between the information you usually have at runtime and the one you have at build or deployment time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
