[
https://issues.apache.org/jira/browse/CAMEL-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17365451#comment-17365451
]
Claus Ibsen commented on CAMEL-16650:
-------------------------------------
Or are we look at something like
https://github.com/apache/camel-examples/blob/main/examples/routetemplate/src/main/resources/application.properties#L27-L33
Where you want to map those 2 route templates to which kamelet file to use as
the template
{code}
camel.route-template[foo].location = classpath:my-foo.kamelet.yaml
camel.route-template[foo].name = one
camel.route-template[foo].greeting = Hello
camel.route-template[bar].location = file:/etc/camel/kamelets/bar.kamelet.yaml
camel.route-template[bar].name = two
camel.route-template[bar].greeting = Bonjour
camel.route-template[bar].my-period = 5s
{code}
Where we can then add *location* as the key to refer to the resource location
of the template file.
> 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)
