nicolaferraro opened a new issue #363:
URL: https://github.com/apache/camel-k-runtime/issues/363
When running an integration using a property like
`{{secret:mysecret/myprop}}`, if the secret is not mounted into the integration
(e.g. using the `--secret mysecret` keyword on `kamel run`), then the property
is evaluated into the string `"mysecret/myprop"`, which is not what the user
expects.
In accordance to what Camel does when using an unmapped property, the
integration should fail and alert the user that the secret has not been bound
(unless the user provides a default, if allowed by the `secret:...' syntax).
If we map to the "secret/prop" string, since it's not common to log secrets
in the routes, the user will just receive some "forbidden" replies from the
remote service and get lost..
----------------------------------------------------------------
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:
[email protected]
