[
https://issues.apache.org/jira/browse/CAMEL-21179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880350#comment-17880350
]
Andrea Cosentino edited comment on CAMEL-21179 at 9/10/24 12:44 PM:
--------------------------------------------------------------------
Hashicorp Vault - Done.
AWS Secrets Manager - Done.
Google Secret Manager - Done, but just to harmonize the syntax, since GCP
Secret Manager doesn't allow to use / in the secret name.
was (Author: ancosen):
Hashicorp Vault - Done.
AWS Secrets Manager - Done.
> Secret Properties Functions: Supporting secret name containing "/"
> ------------------------------------------------------------------
>
> Key: CAMEL-21179
> URL: https://issues.apache.org/jira/browse/CAMEL-21179
> Project: Camel
> Issue Type: New Feature
> Environment:
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.9.0
>
>
> There was a question about Hashicorp Vault support in Camel-Karavan
> https://github.com/apache/camel-karavan/issues/1348
> As of today, this is not feasible, mainly because the "/" symbol is used to
> distinguish between the secret name and the subkey you want to resolve.
> To complete this issue we might need to review the syntax, so something like
> this should be done
> {code:java}
> {{hashicorp:secrets_engine:secret_name/with_slash#subkey:default_value@version}}
> {code}
> This could extended to the other functions, but since it is a breaking change
> it won't go in 4.8.0 and it will need to be documented in the migration guide.
> Essentially we'll need to introduce a different symbol for prefixing the
> subkey.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
