[jira] [Commented] (CAMEL-16650) kamelets: allow to set the location of kamelets

["Claus Ibsen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17365449#comment-17365449 ] 

Claus Ibsen commented on CAMEL-16650:
-------------------------------------

So you are looking for some kind of camel-kamelet component support for mapping a kamelet id to a resource location

There is a location today where you can say

camel.component.kamelet.location = classpath:my-foo.kamelet.yaml , file:/etc/camel/kamelets/bar.kamelet.yaml

And you can of course use wildcards

camel.component.kamelet.location = classpath:*.kamelet.yaml , file:/etc/camel/kamelets/*.kamelet.yaml

Then those are however only discovered on demand, eg if you ask for foo kamelet, then the classpath and file system is scanned for a foo.kamelet.yaml 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)