You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/11/21 18:24:35 UTC

[GitHub] [camel-k-runtime] davsclaus edited a comment on issue #560: camel-kamelet: rimprove global property handling

davsclaus edited a comment on issue #560:
URL: https://github.com/apache/camel-k-runtime/issues/560#issuecomment-731616829


   On top of my head there is some components that have property prefix, like camel-http with http client options
   https://github.com/apache/camel/blob/master/components/camel-http/src/main/java/org/apache/camel/component/http/HttpComponent.java#L406
   
   (mind that the http component is one of the more complex component for this kind) I think rabbitmq and some others have a bit simpler code for this option prefix options.
   
   Maybe we could have something like that, then its
   
   ```
   camel.component.kamelet.template-properties.myTemplate.foo = bar
   camel.component.kamelet.template-properties.myTemplate.code = 1234
   camel.component.kamelet.route-properties.myRoute.foo = bar
   ```
   
   Then `template-properties` and `route-properties` are just a Map which we then use that extract code (see link above) and in the kamelet component we can then do the binding we want.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org