[jira] [Commented] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565937#comment-17565937 ] Andrea Cosentino commented on CAMEL-18267: -- cc [~davsclaus] [~lburgazzoli] > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.x > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18267: - Description: In case of rotation, update, patch etc. We need to trigger a reload. This might be a service running with the properties source or something we could enable on-demand. In this way we could react to events. was:cc [~davsclaus] > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.x > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
Andrea Cosentino created CAMEL-18267: Summary: Vault Support: Trigger a reload of properties from a particular Vault source based on events Key: CAMEL-18267 URL: https://issues.apache.org/jira/browse/CAMEL-18267 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Fix For: 3.x cc [~davsclaus] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
[
https://issues.apache.org/jira/browse/CAMEL-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565101#comment-17565101
]
Andrea Cosentino edited comment on CAMEL-18208 at 7/12/22 5:06 PM:
---
AWS Secret Manager - DONE
Google Secrets Manager - DONE
was (Author: ancosen):
AWS Secret Manager - DONE
> vault: allow to retrieve a specific secret version/revision
> ---
>
> Key: CAMEL-18208
> URL: https://issues.apache.org/jira/browse/CAMEL-18208
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Minor
>
> The vaults for which we have support in Apache Camel support versioned
> secrets (i.e. [1][2]) and it would be very useful to have an option to
> include the verison/revision of the secret in the vault property syntax, as
> example:
> {{aws:username@123}}
> This would mean to get the secret named username and version 123 from the
> aws vault.
> [1]
> https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
> [2]
> https://learn.hashicorp.com/tutorials/vault/versioned-kv#step-7-configure-automatic-data-deletion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18266) Can not use bean uri in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-18266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Feng resolved CAMEL-18266. Resolution: Fixed > Can not use bean uri in xslt component > -- > > Key: CAMEL-18266 > URL: https://issues.apache.org/jira/browse/CAMEL-18266 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-xslt >Affects Versions: 3.18.0 >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It looks like there is a missing bean schema in > ResourceHelper.hasSchema(String uri). And > XsltUriResolver falls back to use classpath schema. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18121) camel-kafka - Upgrade to Kafka clients 3.2.x
[ https://issues.apache.org/jira/browse/CAMEL-18121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-18121: Assignee: Ramu > camel-kafka - Upgrade to Kafka clients 3.2.x > > > Key: CAMEL-18121 > URL: https://issues.apache.org/jira/browse/CAMEL-18121 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18266) Can not use bean uri in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-18266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Feng updated CAMEL-18266: --- Fix Version/s: 3.18.1 3.19.0 > Can not use bean uri in xslt component > -- > > Key: CAMEL-18266 > URL: https://issues.apache.org/jira/browse/CAMEL-18266 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-xslt >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It looks like there is a missing bean schema in > ResourceHelper.hasSchema(String uri). And > XsltUriResolver falls back to use classpath schema. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18266) Can not use bean uri in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-18266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Feng updated CAMEL-18266: --- Affects Version/s: 3.18.0 > Can not use bean uri in xslt component > -- > > Key: CAMEL-18266 > URL: https://issues.apache.org/jira/browse/CAMEL-18266 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-xslt >Affects Versions: 3.18.0 >Reporter: Zheng Feng >Assignee: Zheng Feng >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > It looks like there is a missing bean schema in > ResourceHelper.hasSchema(String uri). And > XsltUriResolver falls back to use classpath schema. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18266) Can not use bean uri in xslt component
Zheng Feng created CAMEL-18266: -- Summary: Can not use bean uri in xslt component Key: CAMEL-18266 URL: https://issues.apache.org/jira/browse/CAMEL-18266 Project: Camel Issue Type: Bug Components: camel-core, camel-xslt Reporter: Zheng Feng Assignee: Zheng Feng It looks like there is a missing bean schema in ResourceHelper.hasSchema(String uri). And XsltUriResolver falls back to use classpath schema. -- This message was sent by Atlassian Jira (v8.20.10#820010)
