[
https://issues.apache.org/jira/browse/CAMEL-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17365455#comment-17365455
]
Claus Ibsen commented on CAMEL-16650:
-------------------------------------
Yeah I think location is a good idea too, then it makes it explicit from where
the template is for those routes to be created.
> kamelets: allow to set the location of kamelets
> -----------------------------------------------
>
> Key: CAMEL-16650
> URL: https://issues.apache.org/jira/browse/CAMEL-16650
> Project: Camel
> Issue Type: Improvement
> Components: camel-kamelet
> Reporter: Luca Burgazzoli
> Assignee: Luca Burgazzoli
> Priority: Minor
> Fix For: 3.11.0
>
>
> Since camel 3.10, kamelets can be discovered from the classpath by name but
> it would be nice to support also loading the kamelets from alternate
> locations, like:
> {code}
> camel.component.kameelts.teamplates[foo] = classpath:my-foo.kamelet.yaml
> camel.component.kameelts.teamplates[bar] =
> file:/etc/camel/kamelets/bar.kamelet.yaml
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
