[jira] [Resolved] (CAMEL-18207) camel-yaml-dsl - YAML Schema should be in schema sub folder
[ https://issues.apache.org/jira/browse/CAMEL-18207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18207. - Resolution: Fixed > camel-yaml-dsl - YAML Schema should be in schema sub folder > --- > > Key: CAMEL-18207 > URL: https://issues.apache.org/jira/browse/CAMEL-18207 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > This conflicts with the json file we have for every JARs that have > description of what the JAR contains. > So we need to move the generated YAML Schema files from root to schema sub > folder -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
Luca Burgazzoli created CAMEL-18208:
---
Summary: 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
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.7#820007)
[jira] [Assigned] (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:all-tabpanel
]
Luca Burgazzoli reassigned CAMEL-18208:
---
Assignee: Andrea Cosentino
> 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.7#820007)
[jira] [Commented] (CAMEL-18204) camel-jbang - Export to Spring Boot or Quarkus should lookup GAV in their specific catalogs
[ https://issues.apache.org/jira/browse/CAMEL-18204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555866#comment-17555866 ] Claus Ibsen commented on CAMEL-18204: - TODO: spring-boot *DONE* TODO: quarkus > camel-jbang - Export to Spring Boot or Quarkus should lookup GAV in their > specific catalogs > --- > > Key: CAMEL-18204 > URL: https://issues.apache.org/jira/browse/CAMEL-18204 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > Today we map 1:1 to a -starter or a camel-quarkus-x dependency. But we should > lookup in the catalog to be sure, and if none exists then fallback to vanilla > camel (and maybe WARN log about this). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18207) camel-yaml-dsl - YAML Schema should be in schema sub folder
Claus Ibsen created CAMEL-18207: --- Summary: camel-yaml-dsl - YAML Schema should be in schema sub folder Key: CAMEL-18207 URL: https://issues.apache.org/jira/browse/CAMEL-18207 Project: Camel Issue Type: Improvement Components: camel-yaml-dsl Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.0 This conflicts with the json file we have for every JARs that have description of what the JAR contains. So we need to move the generated YAML Schema files from root to schema sub folder -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18206) camel-catalog - Add API to check if an artifact exists with a given GAV
[ https://issues.apache.org/jira/browse/CAMEL-18206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18206. - Resolution: Fixed > camel-catalog - Add API to check if an artifact exists with a given GAV > --- > > Key: CAMEL-18206 > URL: https://issues.apache.org/jira/browse/CAMEL-18206 > Project: Camel > Issue Type: Improvement > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.18.0 > > > To make it easy to know if org.apache.camel:camel-xxx exists or not -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18206) camel-catalog - Add API to check if an artifact exists with a given GAV
Claus Ibsen created CAMEL-18206: --- Summary: camel-catalog - Add API to check if an artifact exists with a given GAV Key: CAMEL-18206 URL: https://issues.apache.org/jira/browse/CAMEL-18206 Project: Camel Issue Type: Improvement Components: camel-catalog Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.0 To make it easy to know if org.apache.camel:camel-xxx exists or not -- This message was sent by Atlassian Jira (v8.20.7#820007)
