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/02/11 09:51:15 UTC

[GitHub] [camel-k] nicolaferraro commented on issue #1261: Allow to inject data from externally crafted secrets

nicolaferraro commented on issue #1261: Allow to inject data from externally crafted secrets
URL: https://github.com/apache/camel-k/issues/1261#issuecomment-584553106
 
 
   Yeah, we can still load automatically `.properties` files in the secrets, plus make the content of each entry of a secret available in a `secrets` namespace, so users can reference them by name, e.g.
   
   ```
   camel.component.xxx.password = {{secrets.broker.authToken}}
   ```
   
   Thinking big (for the far future), we can also provide an addon module where we add auto-configuration for connecting to known systems.. this require some effort to be maintained, but a user would be able to do:
   ```
   kamel run integration.groovy --connect activemq:mybroker
   ```
   ... and have all `camel.component.activemq.xxx` properties set.

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


With regards,
Apache Git Services