Hi Yeah there is maybe an use-case for being able to configure a group of parameters, and then refer to this anywhere in yaml-dsl / karavan where you use parameters. And maybe having those in some external fragmented files, so they don't clutter up in application.properties.
On Sat, Mar 2, 2024 at 9:18 AM Mikael Koskinen <mijap...@gmail.com> wrote: > Hi, > > Thank you for the tip, this seems like a good alternative. > > The issue that comes to mind is that we have integrations where we are > transferring issues between multiple Jira instances and directly > configuring the components gives issues in these cases. > > In the best case scenario we hope we could provide properties like: > > ourJira.username = test > ourJira.password = 123456 > ourJira.jiraUrl = https://our.atlassian.com/jira > <https://comp.atlassian.com/jira> > theirJira.username = test > theirJira.password = 123456 > theirJira.jiraUrl = https://our.atlassian.com/jira > <https://comp.atlassian.com/jira> > > And then in the route somehow "auto apply" all these properties into an > endpoint without having to set them one by one. Maybe the ID could be used > in this auto mapping? So something like: > > - route: > from: > uri: jira > id: ourJira-123 > parameters: > type: NEWISSUES > steps: > - to: > uri: jira > id: theirJira-93838 > > > > to 29. helmik. 2024 klo 23.57 Marat Gubaidullin ( > marat.gubaidul...@gmail.com) > kirjoitti: > > > Hello Mikael > > > > I believe that component configuration in application.properties should > > work, so don't need to duplicate in YAML: > > > > camel.component.jira.jira-url=URL > > camel.component.jira.password=PASSWORD > > > > > > Marat > > > > On Thu, Feb 29, 2024 at 9:00 AM Mikael Koskinen <mijap...@gmail.com> > > wrote: > > > > > Hi, > > > > > > Property placeholders allow us to reuse single things like Jira > username > > > and password. But is there a concept in Camel that works with Camel > YAML > > & > > > Karavan where we could reuse "named" endpoint definitions? > > > > > > So the idea is that I could (hopefully in application.properties) > define > > > something like: > > > > > > myjira.username = test > > > myjira.password = 123456 > > > myjira.jiraUrl = https://comp.atlassian.com/jira > > > > > > And then in my route use this "named/keyed" definition when adding the > > Jira > > > component. So something like: > > > > > > - route: > > > from: > > > uri: jira > > > key: "myjira" > > > parameters: > > > type: NEWISSUES > > > steps: > > > - to: > > > uri: kamelet:http-sink > > > parameters: > > > url: https://webhooksite > > > method: POST > > > > > > The idea is that I could apply all the properties defined in the > > > application.properties to the endpoint instead of having to add the > > > properties one by one. > > > > > > I went through the documentation and found something that is almost > > there: > > > > > > > > > https://camel.apache.org/manual/faq/how-do-i-configure-endpoints.html#HowdoIconfigureendpoints-Configuringurisusingendpointwithbeanpropertystyle > > > > > > But then I checked the YAML schema and I don't think it supports these > > > Endpoint-definitions. And if it does, I'm not sure if the Karavan > > designer > > > could keep up with it. > > > > > > So I'm not sure if something like this already exists. Or if I should > use > > > Beans? Or is this a new feature idea. Thanks for any tips in advance. > > > > > > Best regards, > > > Mikael > > > > > > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
