[
https://issues.apache.org/jira/browse/CAMEL-26551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139170#comment-18139170
]
Claus Ibsen commented on CAMEL-26551:
-------------------------------------
PR: https://github.com/apache/camel/pull/29283
Adds the endpoint option {{allowSecretStoreAndKeyFromHeaders}} (default false).
With the default, the secret operation uses only the {{secretStore}} and
{{key}} options of the endpoint. A secret endpoint without a key fails with an
error naming the option when the message has a {{CamelDaprKey}} header, instead
of reading all the secrets of the store. The state operations still use the
{{CamelDaprKey}} header. Upgrade guide entry and a "Headers that override the
endpoint" section on the component page are included.
_Claude Code on behalf of Claus Ibsen (davsclaus)_
> camel-dapr - the secret store and key headers override the endpoint without
> an option to turn that off
> ------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26551
> URL: https://issues.apache.org/jira/browse/CAMEL-26551
> Project: Camel
> Issue Type: Improvement
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Found while fixing CAMEL-26263 (PR #29105).
> For the {{secret}} operation,
> {{DaprConfigurationOptionsProxy.getSecretStore}} and the key lookup take the
> {{CamelDaprSecretStore}} and {{CamelDaprKey}} headers first, and the endpoint
> options only when no header is set. A message can so read another secret, or
> use another secret store, than the endpoint is configured with.
> Proposed, like CAMEL-26273 for camel-clickhouse: honour these two headers for
> the secret operation only with an endpoint option (default false, with an
> upgrade guide entry), and document on the page which headers override the
> endpoint.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
