nicolaferraro commented on issue #549:
URL: https://github.com/apache/camel-kamelets/issues/549#issuecomment-947480209
It's also possible to use auto-secrets in KameletBindings, like you do in
java routes. The place you put the configuration name is in the special `id`
property. Something like this should work:
```yaml
# ...
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: my-company-log-sink
properties:
id: mynamedconfig # The special "id" property links the binding to the
secret you defined above
```
We should document this. There's an example in the e2e tests:
https://github.com/apache/camel-k/tree/92c860599760f8d74c63c5f71e689e0a7b374438/e2e/yaks/common/kamelet-binding-autoload
The only problem of the solution described by @oscerd is that those
properties become global in the KameletBinding, so any Kamelet in the binding
that has e.g. and "authorizationToken" parameter gets the global value, while
the secret autoload strategy does not suffer from this issue.
--
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.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
