[jira] [Resolved] (CAMEL-21249) Camel-Kamelets: Move Kamelets utils in Camel Kamelets component
[ https://issues.apache.org/jira/browse/CAMEL-21249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21249. -- Resolution: Fixed > Camel-Kamelets: Move Kamelets utils in Camel Kamelets component > --- > > Key: CAMEL-21249 > URL: https://issues.apache.org/jira/browse/CAMEL-21249 > Project: Camel > Issue Type: New Feature > Components: camel-kamelet >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21265) Create ApplicationEnvironmentPreparedEvent for Vault components
[
https://issues.apache.org/jira/browse/CAMEL-21265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887956#comment-17887956
]
Andrea Cosentino commented on CAMEL-21265:
--
Thanks [~Federico Mariani] for the Hashicorp part.
I'm going to do the same for AWS, GCP and Azure
> Create ApplicationEnvironmentPreparedEvent for Vault components
> ---
>
> Key: CAMEL-21265
> URL: https://issues.apache.org/jira/browse/CAMEL-21265
> Project: Camel
> Issue Type: New Feature
> Components: camel-hashicorp-vault, camel-spring-boot
>Reporter: Federico Mariani
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.x
>
>
> As a user, I would like to use vaults and easily resolve properties as I do
> in Camel routes, but during Spring startup, setting a property like
> _spring.datasource.password={{aws:...}}_ should be possible.
> This is the list of the components that may benefit from it:
> {code:java}
> AWS Secret Manager
> Google Secrets Manager
> Azure Key Vault
> Hashicorp Vault
> {code}
> Something similar was done for the camel-jasypt-starter component
> https://github.com/apache/camel-spring-boot/commit/18116fc727d747b3ecd63586f64d21b452deb03c#diff-ca96b9726dc6672f349a50ca707d332d93aa716def7a553948b4622a9912ae57R21
>
> So far it was done for Camel Spring Boot only, but it would be nice to
> investigate if something similar can be done for Camel Quarkus.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21262) Camel-AWS2-S3: Explicitly add Producer operations HeadObject and HeadBucket
[ https://issues.apache.org/jira/browse/CAMEL-21262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21262. -- Resolution: Fixed > Camel-AWS2-S3: Explicitly add Producer operations HeadObject and HeadBucket > > > Key: CAMEL-21262 > URL: https://issues.apache.org/jira/browse/CAMEL-21262 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21334) Camel-opensearch - Provide ppc64le arch support
[ https://issues.apache.org/jira/browse/CAMEL-21334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21334. -- Resolution: Fixed > Camel-opensearch - Provide ppc64le arch support > --- > > Key: CAMEL-21334 > URL: https://issues.apache.org/jira/browse/CAMEL-21334 > Project: Camel > Issue Type: Task > Components: camel-opensearch >Reporter: Anushka Juli >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > Attachments: camel-opensearch-logs-on-x86.txt, > opensearch_build_success_logs.txt, opensearch_test_infra_logs.txt > > > h1. We want to provide ppc64le arch support to camel-opensearch in the camel > component -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21334) Camel-opensearch - Provide ppc64le arch support
[ https://issues.apache.org/jira/browse/CAMEL-21334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21334: - Fix Version/s: 4.9.0 > Camel-opensearch - Provide ppc64le arch support > --- > > Key: CAMEL-21334 > URL: https://issues.apache.org/jira/browse/CAMEL-21334 > Project: Camel > Issue Type: Task > Components: camel-opensearch >Reporter: Anushka Juli >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > Attachments: camel-opensearch-logs-on-x86.txt, > opensearch_build_success_logs.txt, opensearch_test_infra_logs.txt > > > h1. We want to provide ppc64le arch support to camel-opensearch in the camel > component -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21334) Camel-opensearch - Provide ppc64le arch support
[ https://issues.apache.org/jira/browse/CAMEL-21334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21334: Assignee: Andrea Cosentino > Camel-opensearch - Provide ppc64le arch support > --- > > Key: CAMEL-21334 > URL: https://issues.apache.org/jira/browse/CAMEL-21334 > Project: Camel > Issue Type: Task > Components: camel-opensearch >Reporter: Anushka Juli >Assignee: Andrea Cosentino >Priority: Minor > Attachments: camel-opensearch-logs-on-x86.txt, > opensearch_build_success_logs.txt, opensearch_test_infra_logs.txt > > > h1. We want to provide ppc64le arch support to camel-opensearch in the camel > component -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21311) NATS: Automatically added nats:// prefix in servers-parameter blocks the usage of NATS' built-in Websocket support
[ https://issues.apache.org/jira/browse/CAMEL-21311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21311. -- Resolution: Fixed > NATS: Automatically added nats:// prefix in servers-parameter blocks the > usage of NATS' built-in Websocket support > -- > > Key: CAMEL-21311 > URL: https://issues.apache.org/jira/browse/CAMEL-21311 > Project: Camel > Issue Type: Improvement > Components: camel-nats >Affects Versions: 4.8.0 >Reporter: Mikael Koskinen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > The current code in NatsConfiguration.java adds the nats:// -prefix > automatically to the server connection string: > String prefix = "nats://"; > This causes issues, because NATS supports other protocols like Websockets, > where the prefix is ws:// or wss:// instead of nats:// > Looking at the examples provided by NATS, the prefix is something that the > user of the NATS should provide as it defines the protocol between the client > and the server. For example: > [https://natsbyexample.com/examples/messaging/pub-sub/java] > I was wondering if the auto-prefixing could be removed but then that would be > a breaking change. > Maybe a new configuration parameter could be added for defining the prefix > (the protocol) and that could default to nats:// like currently? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21324) Camel-AWS-Secret-Manager: for context reloading on secret refresh we should check also UpdateSecret Event
[ https://issues.apache.org/jira/browse/CAMEL-21324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21324. -- Resolution: Fixed > Camel-AWS-Secret-Manager: for context reloading on secret refresh we should > check also UpdateSecret Event > - > > Key: CAMEL-21324 > URL: https://issues.apache.org/jira/browse/CAMEL-21324 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > This is true for both the approach, the cloud trail one and the eventbridge > one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21323) Camel-AWS-Secrets-Manager: Add a PutSecretValue operation to producer
[ https://issues.apache.org/jira/browse/CAMEL-21323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21323. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Add a PutSecretValue operation to producer > - > > Key: CAMEL-21323 > URL: https://issues.apache.org/jira/browse/CAMEL-21323 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21324) Camel-AWS-Secret-Manager: for context reloading on secret refresh we should check also UpdateSecret Event
Andrea Cosentino created CAMEL-21324: Summary: Camel-AWS-Secret-Manager: for context reloading on secret refresh we should check also UpdateSecret Event Key: CAMEL-21324 URL: https://issues.apache.org/jira/browse/CAMEL-21324 Project: Camel Issue Type: New Feature Components: camel-aws2 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 This is true for both the approach, the cloud trail one and the eventbridge one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21323) Camel-AWS-Secrets-Manager: Add a PutSecretValue operation to producer
Andrea Cosentino created CAMEL-21323: Summary: Camel-AWS-Secrets-Manager: Add a PutSecretValue operation to producer Key: CAMEL-21323 URL: https://issues.apache.org/jira/browse/CAMEL-21323 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21312) camel-debezium - Upgrade to 3.0
[ https://issues.apache.org/jira/browse/CAMEL-21312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21312. -- Resolution: Fixed > camel-debezium - Upgrade to 3.0 > --- > > Key: CAMEL-21312 > URL: https://issues.apache.org/jira/browse/CAMEL-21312 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-debezium >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21312) camel-debezium - Upgrade to 3.0
[ https://issues.apache.org/jira/browse/CAMEL-21312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21312: Assignee: Andrea Cosentino > camel-debezium - Upgrade to 3.0 > --- > > Key: CAMEL-21312 > URL: https://issues.apache.org/jira/browse/CAMEL-21312 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-debezium >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21311) NATS: Automatically added nats:// prefix in servers-parameter blocks the usage of NATS' built-in Websocket support
[ https://issues.apache.org/jira/browse/CAMEL-21311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21311: Assignee: Andrea Cosentino > NATS: Automatically added nats:// prefix in servers-parameter blocks the > usage of NATS' built-in Websocket support > -- > > Key: CAMEL-21311 > URL: https://issues.apache.org/jira/browse/CAMEL-21311 > Project: Camel > Issue Type: Improvement > Components: camel-nats >Affects Versions: 4.8.0 >Reporter: Mikael Koskinen >Assignee: Andrea Cosentino >Priority: Major > > The current code in NatsConfiguration.java adds the nats:// -prefix > automatically to the server connection string: > String prefix = "nats://"; > This causes issues, because NATS supports other protocols like Websockets, > where the prefix is ws:// or wss:// instead of nats:// > Looking at the examples provided by NATS, the prefix is something that the > user of the NATS should provide as it defines the protocol between the client > and the server. For example: > [https://natsbyexample.com/examples/messaging/pub-sub/java] > I was wondering if the auto-prefixing could be removed but then that would be > a breaking change. > Maybe a new configuration parameter could be added for defining the prefix > (the protocol) and that could default to nats:// like currently? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21311) NATS: Automatically added nats:// prefix in servers-parameter blocks the usage of NATS' built-in Websocket support
[ https://issues.apache.org/jira/browse/CAMEL-21311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21311: - Fix Version/s: 4.9.0 > NATS: Automatically added nats:// prefix in servers-parameter blocks the > usage of NATS' built-in Websocket support > -- > > Key: CAMEL-21311 > URL: https://issues.apache.org/jira/browse/CAMEL-21311 > Project: Camel > Issue Type: Improvement > Components: camel-nats >Affects Versions: 4.8.0 >Reporter: Mikael Koskinen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > The current code in NatsConfiguration.java adds the nats:// -prefix > automatically to the server connection string: > String prefix = "nats://"; > This causes issues, because NATS supports other protocols like Websockets, > where the prefix is ws:// or wss:// instead of nats:// > Looking at the examples provided by NATS, the prefix is something that the > user of the NATS should provide as it defines the protocol between the client > and the server. For example: > [https://natsbyexample.com/examples/messaging/pub-sub/java] > I was wondering if the auto-prefixing could be removed but then that would be > a breaking change. > Maybe a new configuration parameter could be added for defining the prefix > (the protocol) and that could default to nats:// like currently? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21311) NATS: Automatically added nats:// prefix in servers-parameter blocks the usage of NATS' built-in Websocket support
[ https://issues.apache.org/jira/browse/CAMEL-21311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886615#comment-17886615 ] Andrea Cosentino commented on CAMEL-21311: -- It makes sense, I think this would also be not invasive for eventually backporting to 4.8.x, because I see this more as limitation/bug, not really an improvement. cc [~cib...@e-ma.net] > NATS: Automatically added nats:// prefix in servers-parameter blocks the > usage of NATS' built-in Websocket support > -- > > Key: CAMEL-21311 > URL: https://issues.apache.org/jira/browse/CAMEL-21311 > Project: Camel > Issue Type: Improvement > Components: camel-nats >Affects Versions: 4.8.0 >Reporter: Mikael Koskinen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > The current code in NatsConfiguration.java adds the nats:// -prefix > automatically to the server connection string: > String prefix = "nats://"; > This causes issues, because NATS supports other protocols like Websockets, > where the prefix is ws:// or wss:// instead of nats:// > Looking at the examples provided by NATS, the prefix is something that the > user of the NATS should provide as it defines the protocol between the client > and the server. For example: > [https://natsbyexample.com/examples/messaging/pub-sub/java] > I was wondering if the auto-prefixing could be removed but then that would be > a breaking change. > Maybe a new configuration parameter could be added for defining the prefix > (the protocol) and that could default to nats:// like currently? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21275) Camel-Clickup Spring Boot Starter
[ https://issues.apache.org/jira/browse/CAMEL-21275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21275. -- Resolution: Fixed > Camel-Clickup Spring Boot Starter > - > > Key: CAMEL-21275 > URL: https://issues.apache.org/jira/browse/CAMEL-21275 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21287) Camel-Azure-Files: missing header for AZURE_IDENTITY
[ https://issues.apache.org/jira/browse/CAMEL-21287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21287: - Summary: Camel-Azure-Files: missing header for AZURE_IDENTITY (was: [camel-azure-files]: missing header for AZURE_IDENTITY) > Camel-Azure-Files: missing header for AZURE_IDENTITY > > > Key: CAMEL-21287 > URL: https://issues.apache.org/jira/browse/CAMEL-21287 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.8.0 >Reporter: Sven >Priority: Major > > The API calls to azure fileshares using a bearer token > (credentialType=AZURE_IDENTITY) requires the header x-ms-file-request-intent > to be set. Currently it seems the API only supports the value 'backup'. > I'll create a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21287) Camel-Azure-Files: missing header for AZURE_IDENTITY
[ https://issues.apache.org/jira/browse/CAMEL-21287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21287: - Priority: Minor (was: Major) > Camel-Azure-Files: missing header for AZURE_IDENTITY > > > Key: CAMEL-21287 > URL: https://issues.apache.org/jira/browse/CAMEL-21287 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.8.0 >Reporter: Sven >Priority: Minor > > The API calls to azure fileshares using a bearer token > (credentialType=AZURE_IDENTITY) requires the header x-ms-file-request-intent > to be set. Currently it seems the API only supports the value 'backup'. > I'll create a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21275) Camel-Clickup Spring Boot Starter
Andrea Cosentino created CAMEL-21275: Summary: Camel-Clickup Spring Boot Starter Key: CAMEL-21275 URL: https://issues.apache.org/jira/browse/CAMEL-21275 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21244) camel-clickup component
[
https://issues.apache.org/jira/browse/CAMEL-21244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21244:
-
Summary: camel-clickup component (was: camel-clickup)
> camel-clickup component
> ---
>
> Key: CAMEL-21244
> URL: https://issues.apache.org/jira/browse/CAMEL-21244
> Project: Camel
> Issue Type: New Feature
>Reporter: Nicolò Scarpa
>Priority: Major
> Fix For: 4.9.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> A new Camel component to receive events from webhooks by adopting the
> {{camel-webhook}} meta-component.
> ClickUp developer guide for webhooks:
> [https://clickup.com/api/developer-portal/webhooks/]
> The component may be further extended to support read/write to ClickUp REST
> APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21244) camel-clickup component
[
https://issues.apache.org/jira/browse/CAMEL-21244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-21244:
Assignee: Andrea Cosentino
> camel-clickup component
> ---
>
> Key: CAMEL-21244
> URL: https://issues.apache.org/jira/browse/CAMEL-21244
> Project: Camel
> Issue Type: New Feature
>Reporter: Nicolò Scarpa
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.9.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> A new Camel component to receive events from webhooks by adopting the
> {{camel-webhook}} meta-component.
> ClickUp developer guide for webhooks:
> [https://clickup.com/api/developer-portal/webhooks/]
> The component may be further extended to support read/write to ClickUp REST
> APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21244) camel-clickup component
[
https://issues.apache.org/jira/browse/CAMEL-21244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21244.
--
Resolution: Fixed
> camel-clickup component
> ---
>
> Key: CAMEL-21244
> URL: https://issues.apache.org/jira/browse/CAMEL-21244
> Project: Camel
> Issue Type: New Feature
>Reporter: Nicolò Scarpa
>Priority: Major
> Fix For: 4.9.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> A new Camel component to receive events from webhooks by adopting the
> {{camel-webhook}} meta-component.
> ClickUp developer guide for webhooks:
> [https://clickup.com/api/developer-portal/webhooks/]
> The component may be further extended to support read/write to ClickUp REST
> APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21253) Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder for metrics of the Scheduler enable/disable
[ https://issues.apache.org/jira/browse/CAMEL-21253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21253: - Fix Version/s: 4.8.1 > Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder for metrics of the > Scheduler enable/disable > - > > Key: CAMEL-21253 > URL: https://issues.apache.org/jira/browse/CAMEL-21253 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.1, 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21265) Create ApplicationEnvironmentPreparedEvent for Vault components
[
https://issues.apache.org/jira/browse/CAMEL-21265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21265:
-
Fix Version/s: 4.x
> Create ApplicationEnvironmentPreparedEvent for Vault components
> ---
>
> Key: CAMEL-21265
> URL: https://issues.apache.org/jira/browse/CAMEL-21265
> Project: Camel
> Issue Type: New Feature
> Components: camel-hashicorp-vault, camel-spring-boot
>Reporter: Federico Mariani
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.x
>
>
> As a user, I would like to use vaults and easily resolve properties as I do
> in Camel routes, but during Spring startup, setting a property like
> _spring.datasource.password={{aws:...}}_ should be possible.
> This is the list of the components that may benefit from it:
> {code:java}
> AWS Secret Manager
> Google Secrets Manager
> Azure Key Vault
> Hashicorp Vault
> {code}
> Something similar was done for the camel-jasypt-starter component
> https://github.com/apache/camel-spring-boot/commit/18116fc727d747b3ecd63586f64d21b452deb03c#diff-ca96b9726dc6672f349a50ca707d332d93aa716def7a553948b4622a9912ae57R21
>
> So far it was done for Camel Spring Boot only, but it would be nice to
> investigate if something similar can be done for Camel Quarkus.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21265) Create ApplicationEnvironmentPreparedEvent for Vault components
[
https://issues.apache.org/jira/browse/CAMEL-21265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-21265:
Assignee: Andrea Cosentino
> Create ApplicationEnvironmentPreparedEvent for Vault components
> ---
>
> Key: CAMEL-21265
> URL: https://issues.apache.org/jira/browse/CAMEL-21265
> Project: Camel
> Issue Type: New Feature
> Components: camel-hashicorp-vault, camel-spring-boot
>Reporter: Federico Mariani
>Assignee: Andrea Cosentino
>Priority: Major
>
> As a user, I would like to use vaults and easily resolve properties as I do
> in Camel routes, but during Spring startup, setting a property like
> _spring.datasource.password={{aws:...}}_ should be possible.
> This is the list of the components that may benefit from it:
> {code:java}
> AWS Secret Manager
> Google Secrets Manager
> Azure Key Vault
> Hashicorp Vault
> {code}
> Something similar was done for the camel-jasypt-starter component
> https://github.com/apache/camel-spring-boot/commit/18116fc727d747b3ecd63586f64d21b452deb03c#diff-ca96b9726dc6672f349a50ca707d332d93aa716def7a553948b4622a9912ae57R21
>
> So far it was done for Camel Spring Boot only, but it would be nice to
> investigate if something similar can be done for Camel Quarkus.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21262) Camel-AWS2-S3: Explicitly add Producer operations HeadObject and HeadBucket
Andrea Cosentino created CAMEL-21262: Summary: Camel-AWS2-S3: Explicitly add Producer operations HeadObject and HeadBucket Key: CAMEL-21262 URL: https://issues.apache.org/jira/browse/CAMEL-21262 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21251) Camel-AWS2-S3: Support Conditional Reads on producer operations
[ https://issues.apache.org/jira/browse/CAMEL-21251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21251. -- Resolution: Fixed > Camel-AWS2-S3: Support Conditional Reads on producer operations > --- > > Key: CAMEL-21251 > URL: https://issues.apache.org/jira/browse/CAMEL-21251 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-reads.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21232) camel-http - Upgrade to 5.3 causes test failures
[ https://issues.apache.org/jira/browse/CAMEL-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884544#comment-17884544 ] Andrea Cosentino commented on CAMEL-21232: -- Failing, we had to revert. > camel-http - Upgrade to 5.3 causes test failures > > > Key: CAMEL-21232 > URL: https://issues.apache.org/jira/browse/CAMEL-21232 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-http >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > The 5.3 release causes some test failures. We would need to investigate why > and if something needs to be changed in camel-http, or its some new bugs in > http 5.3. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21232) camel-http - Upgrade to 5.3 causes test failures
[ https://issues.apache.org/jira/browse/CAMEL-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21232: - Fix Version/s: 4.9.0 (was: 4.x) > camel-http - Upgrade to 5.3 causes test failures > > > Key: CAMEL-21232 > URL: https://issues.apache.org/jira/browse/CAMEL-21232 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-http >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.9.0 > > > The 5.3 release causes some test failures. We would need to investigate why > and if something needs to be changed in camel-http, or its some new bugs in > http 5.3. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21232) camel-http - Upgrade to 5.3 causes test failures
[ https://issues.apache.org/jira/browse/CAMEL-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884539#comment-17884539 ] Andrea Cosentino commented on CAMEL-21232: -- We merged this https://github.com/apache/camel/pull/15634 with 5.4, from Github Actions everything seems fine, let's see on ASF CI. > camel-http - Upgrade to 5.3 causes test failures > > > Key: CAMEL-21232 > URL: https://issues.apache.org/jira/browse/CAMEL-21232 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-http >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > The 5.3 release causes some test failures. We would need to investigate why > and if something needs to be changed in camel-http, or its some new bugs in > http 5.3. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21232) camel-http - Upgrade to 5.3 causes test failures
[ https://issues.apache.org/jira/browse/CAMEL-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21232: Assignee: Andrea Cosentino > camel-http - Upgrade to 5.3 causes test failures > > > Key: CAMEL-21232 > URL: https://issues.apache.org/jira/browse/CAMEL-21232 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-http >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > The 5.3 release causes some test failures. We would need to investigate why > and if something needs to be changed in camel-http, or its some new bugs in > http 5.3. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21254) Camel-Google-Big-Query: Cannot set a different projectId from default in particular conditions
[ https://issues.apache.org/jira/browse/CAMEL-21254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21254: - Summary: Camel-Google-Big-Query: Cannot set a different projectId from default in particular conditions (was: Camel-Google-Big-Query: Cannot set a different projectId from default) > Camel-Google-Big-Query: Cannot set a different projectId from default in > particular conditions > -- > > Key: CAMEL-21254 > URL: https://issues.apache.org/jira/browse/CAMEL-21254 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel.20google-biqquery > The use case is particular, the user needs to move stuff from one GCP project > to another one, in Kubernetes environment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21253) Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder for metrics of the Scheduler enable/disable
[ https://issues.apache.org/jira/browse/CAMEL-21253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21253. -- Resolution: Fixed > Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder for metrics of the > Scheduler enable/disable > - > > Key: CAMEL-21253 > URL: https://issues.apache.org/jira/browse/CAMEL-21253 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21253) Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder for metrics of the Scheduler enable/disable
[ https://issues.apache.org/jira/browse/CAMEL-21253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21253: - Summary: Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder for metrics of the Scheduler enable/disable (was: Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder of the Scheduler configurable as instance or by specifying fields) > Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder for metrics of the > Scheduler enable/disable > - > > Key: CAMEL-21253 > URL: https://issues.apache.org/jira/browse/CAMEL-21253 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21254) Camel-Google-Big-Query: Cannot set a different projectId from default
[ https://issues.apache.org/jira/browse/CAMEL-21254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21254: - Description: https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel.20google-biqquery The use case is particular, the user needs to move stuff from one GCP project to another one, in Kubernetes environment. was:https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel.20google-biqquery > Camel-Google-Big-Query: Cannot set a different projectId from default > - > > Key: CAMEL-21254 > URL: https://issues.apache.org/jira/browse/CAMEL-21254 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel.20google-biqquery > The use case is particular, the user needs to move stuff from one GCP project > to another one, in Kubernetes environment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21254) Camel-Google-Big-Query: Cannot set a different projectId from default
[ https://issues.apache.org/jira/browse/CAMEL-21254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21254: - Issue Type: Improvement (was: Bug) > Camel-Google-Big-Query: Cannot set a different projectId from default > - > > Key: CAMEL-21254 > URL: https://issues.apache.org/jira/browse/CAMEL-21254 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel.20google-biqquery -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21252) Add checking for non .*-versions to sync-properties-maven-plugin
[
https://issues.apache.org/jira/browse/CAMEL-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21252:
-
Fix Version/s: 4.4.4
4.8.1
4.9.0
> Add checking for non .*-versions to sync-properties-maven-plugin
>
>
> Key: CAMEL-21252
> URL: https://issues.apache.org/jira/browse/CAMEL-21252
> Project: Camel
> Issue Type: Task
> Components: tooling
>Affects Versions: 4.8.0
>Reporter: Thomas Cunningham
>Assignee: Thomas Cunningham
>Priority: Major
> Fix For: 4.4.4, 4.8.1, 4.9.0
>
>
> sync-properties-maven-plugin only synchronizes properties that fit the
> pattern
> {code:java}
> @Parameter(defaultValue = ".*-version") {code}
> which means that properties like
> {code:java}
> 8.5.7 {code}
> [https://github.com/apache/camel/blob/main/parent/pom.xml#L504C9-L504C45]
> are allowed but do not get synced to camel-dependencies. I'd like to add
> a check for properties not meeting that pattern and fix the zeebe.version->
> zeebe-version so that it gets generated in camel-dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21254) Camel-Google-Big-Query: Cannot set a different projectId from default
Andrea Cosentino created CAMEL-21254: Summary: Camel-Google-Big-Query: Cannot set a different projectId from default Key: CAMEL-21254 URL: https://issues.apache.org/jira/browse/CAMEL-21254 Project: Camel Issue Type: Bug Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.1, 4.9.0 https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/camel.20google-biqquery -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21253) Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder of the Scheduler configurable as instance or by specifying fields
Andrea Cosentino created CAMEL-21253: Summary: Camel AWS Kinesis: KCL Consumers, make the ConfigsBuilder of the Scheduler configurable as instance or by specifying fields Key: CAMEL-21253 URL: https://issues.apache.org/jira/browse/CAMEL-21253 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21248) Camel-Aws2-S3: Support Conditional Writes
[ https://issues.apache.org/jira/browse/CAMEL-21248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21248. -- Resolution: Fixed > Camel-Aws2-S3: Support Conditional Writes > -- > > Key: CAMEL-21248 > URL: https://issues.apache.org/jira/browse/CAMEL-21248 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-writes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21251) Camel-AWS2-S3: Support Conditional Reads on producer operations
Andrea Cosentino created CAMEL-21251: Summary: Camel-AWS2-S3: Support Conditional Reads on producer operations Key: CAMEL-21251 URL: https://issues.apache.org/jira/browse/CAMEL-21251 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-reads.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21249) Camel-Kamelets: Move Kamelets utils in Camel Kamelets component
Andrea Cosentino created CAMEL-21249: Summary: Camel-Kamelets: Move Kamelets utils in Camel Kamelets component Key: CAMEL-21249 URL: https://issues.apache.org/jira/browse/CAMEL-21249 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21248) Camel-Aws2-S3: Support Conditional Writes
Andrea Cosentino created CAMEL-21248: Summary: Camel-Aws2-S3: Support Conditional Writes Key: CAMEL-21248 URL: https://issues.apache.org/jira/browse/CAMEL-21248 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-writes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21245) Specific langchain4j tokenizer are missing in Catalog
[ https://issues.apache.org/jira/browse/CAMEL-21245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883256#comment-17883256 ] Andrea Cosentino commented on CAMEL-21245: -- Essentially there is no model for the different tokenizers implementation, so there couldn't be any YAML generated code. The only model is for the Langchain4jTokenizer itself. > Specific langchain4j tokenizer are missing in Catalog > - > > Key: CAMEL-21245 > URL: https://issues.apache.org/jira/browse/CAMEL-21245 > Project: Camel > Issue Type: Bug > Components: camel-langchain4j >Reporter: Aurélien Pupier >Priority: Major > > byCharacter, byLine, byWord, bySentence, byParagraph are not part of the > Camel catalog for langchain4j tokenizer > https://github.com/apache/camel/blob/bd427fb7b288011aafafce88076e7792168f8da7/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/langChain4j.json#L15 > Or they are missing because the Yaml language is not supporting to specify > them? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21107) Camel-Kubernetes: Add ability to add annotation to create resources operation
[ https://issues.apache.org/jira/browse/CAMEL-21107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878107#comment-17878107 ] Andrea Cosentino edited comment on CAMEL-21107 at 9/17/24 8:36 AM: --- Secrets - Done Job - Done Cron jobs - Done Namespaces - Done was (Author: ancosen): Secrets - Done Job - Done Cron jobs - Done > Camel-Kubernetes: Add ability to add annotation to create resources operation > - > > Key: CAMEL-21107 > URL: https://issues.apache.org/jira/browse/CAMEL-21107 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21107) Camel-Kubernetes: Add ability to add annotation to create resources operation
[ https://issues.apache.org/jira/browse/CAMEL-21107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878107#comment-17878107 ] Andrea Cosentino edited comment on CAMEL-21107 at 9/16/24 10:41 AM: Secrets - Done Job - Done Cron jobs - Done was (Author: ancosen): Secrets - Done Job - Done > Camel-Kubernetes: Add ability to add annotation to create resources operation > - > > Key: CAMEL-21107 > URL: https://issues.apache.org/jira/browse/CAMEL-21107 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21207) Camel-Opensearch: Provide a parameter to set HostNameVerifier on client
[ https://issues.apache.org/jira/browse/CAMEL-21207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21207. -- Resolution: Fixed > Camel-Opensearch: Provide a parameter to set HostNameVerifier on client > --- > > Key: CAMEL-21207 > URL: https://issues.apache.org/jira/browse/CAMEL-21207 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21207) Camel-Opensearch: Provide a parameter to set HostNameVerifier on client
Andrea Cosentino created CAMEL-21207: Summary: Camel-Opensearch: Provide a parameter to set HostNameVerifier on client Key: CAMEL-21207 URL: https://issues.apache.org/jira/browse/CAMEL-21207 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21206) Camel-Google-Storage: Support prefix in ListObjects operation
[ https://issues.apache.org/jira/browse/CAMEL-21206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21206. -- Resolution: Fixed > Camel-Google-Storage: Support prefix in ListObjects operation > - > > Key: CAMEL-21206 > URL: https://issues.apache.org/jira/browse/CAMEL-21206 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21206) Camel-Google-Storage: Support prefix in ListObjects operation
Andrea Cosentino created CAMEL-21206: Summary: Camel-Google-Storage: Support prefix in ListObjects operation Key: CAMEL-21206 URL: https://issues.apache.org/jira/browse/CAMEL-21206 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21198) Create an IBM Secrets Manager component
Andrea Cosentino created CAMEL-21198: Summary: Create an IBM Secrets Manager component Key: CAMEL-21198 URL: https://issues.apache.org/jira/browse/CAMEL-21198 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x https://github.com/IBM/secrets-manager-java-sdk -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21186) AWS Secrets Manager: Support Batch Retrieval for Secrets
[ https://issues.apache.org/jira/browse/CAMEL-21186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21186. -- Resolution: Fixed > AWS Secrets Manager: Support Batch Retrieval for Secrets > > > Key: CAMEL-21186 > URL: https://issues.apache.org/jira/browse/CAMEL-21186 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > > https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_BatchGetSecretValue.html > This will help on the cost side. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20468) Camel-AWS-Bedrock: Support available models
[ https://issues.apache.org/jira/browse/CAMEL-20468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20468: - Fix Version/s: 4.8.0 (was: 4.x) > Camel-AWS-Bedrock: Support available models > --- > > Key: CAMEL-20468 > URL: https://issues.apache.org/jira/browse/CAMEL-20468 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20468) Camel-AWS-Bedrock: Support available models
[ https://issues.apache.org/jira/browse/CAMEL-20468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20468. -- Resolution: Fixed > Camel-AWS-Bedrock: Support available models > --- > > Key: CAMEL-20468 > URL: https://issues.apache.org/jira/browse/CAMEL-20468 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21179) Secret Properties Functions: Supporting secret name containing "/"
[
https://issues.apache.org/jira/browse/CAMEL-21179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21179.
--
Resolution: Fixed
> 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)
[jira] [Comment Edited] (CAMEL-21179) Secret Properties Functions: Supporting secret name containing "/"
[
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 2:10 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.
Azure Key Vault - Done, but just to harmonize the syntax, since Azure Key
Vault doesn't allow to use / in the secret name.
was (Author: ancosen):
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.
> 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)
[jira] [Comment Edited] (CAMEL-21179) Secret Properties Functions: Supporting secret name containing "/"
[
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)
[jira] [Updated] (CAMEL-21186) AWS Secrets Manager: Support Batch Retrieval for Secrets
[ https://issues.apache.org/jira/browse/CAMEL-21186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21186: - Priority: Minor (was: Major) > AWS Secrets Manager: Support Batch Retrieval for Secrets > > > Key: CAMEL-21186 > URL: https://issues.apache.org/jira/browse/CAMEL-21186 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > > https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_BatchGetSecretValue.html > This will help on the cost side. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21186) AWS Secrets Manager: Support Batch Retrieval for Secrets
Andrea Cosentino created CAMEL-21186: Summary: AWS Secrets Manager: Support Batch Retrieval for Secrets Key: CAMEL-21186 URL: https://issues.apache.org/jira/browse/CAMEL-21186 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_BatchGetSecretValue.html This will help on the cost side. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21172) Camel-Jbang Dev Console: Add Hashicorp Vault support
[ https://issues.apache.org/jira/browse/CAMEL-21172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21172. -- Resolution: Fixed > Camel-Jbang Dev Console: Add Hashicorp Vault support > > > Key: CAMEL-21172 > URL: https://issues.apache.org/jira/browse/CAMEL-21172 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21179) Secret Properties Functions: Supporting secret name containing "/"
[
https://issues.apache.org/jira/browse/CAMEL-21179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21179:
-
Description:
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.
was:
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.
> 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.x
>
>
> 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)
[jira] [Updated] (CAMEL-20726) Camel-Pinecone: Improve Documentation
[ https://issues.apache.org/jira/browse/CAMEL-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20726: - Fix Version/s: 4.9.0 (was: 4.8.0) > Camel-Pinecone: Improve Documentation > - > > Key: CAMEL-20726 > URL: https://issues.apache.org/jira/browse/CAMEL-20726 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21173) Camel-Jbang Dev Console: Add Kubernetes Vault support
Andrea Cosentino created CAMEL-21173: Summary: Camel-Jbang Dev Console: Add Kubernetes Vault support Key: CAMEL-21173 URL: https://issues.apache.org/jira/browse/CAMEL-21173 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21172) Camel-Jbang Dev Console: Add Hashicorp Vault support
Andrea Cosentino created CAMEL-21172: Summary: Camel-Jbang Dev Console: Add Hashicorp Vault support Key: CAMEL-21172 URL: https://issues.apache.org/jira/browse/CAMEL-21172 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21169) Kubernetes Secrets: Trigger context reloading on update - Documentation
Andrea Cosentino created CAMEL-21169: Summary: Kubernetes Secrets: Trigger context reloading on update - Documentation Key: CAMEL-21169 URL: https://issues.apache.org/jira/browse/CAMEL-21169 Project: Camel Issue Type: Sub-task Components: camel-kubernetes Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21142) Kubernetes Secrets: Trigger context reloading on update
[ https://issues.apache.org/jira/browse/CAMEL-21142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21142: - Fix Version/s: 4.8.0 (was: 4.9.0) > Kubernetes Secrets: Trigger context reloading on update > --- > > Key: CAMEL-21142 > URL: https://issues.apache.org/jira/browse/CAMEL-21142 > Project: Camel > Issue Type: New Feature > Components: camel-kubernetes >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.8.0 > > > We have already reload tasks in AWS, GCP and Azure Key Vault for triggering a > context reload on particular events. The aim of this issue is to do the same > in a cloud context, when we are using a particular secret or configmap from > the Kubernetes environment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21142) Kubernetes Secrets: Trigger context reloading on update
[ https://issues.apache.org/jira/browse/CAMEL-21142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21142: - Summary: Kubernetes Secrets: Trigger context reloading on update (was: Kubernetes Secrets/Configmap: Trigger context reloading on update) > Kubernetes Secrets: Trigger context reloading on update > --- > > Key: CAMEL-21142 > URL: https://issues.apache.org/jira/browse/CAMEL-21142 > Project: Camel > Issue Type: New Feature > Components: camel-kubernetes >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > > We have already reload tasks in AWS, GCP and Azure Key Vault for triggering a > context reload on particular events. The aim of this issue is to do the same > in a cloud context, when we are using a particular secret or configmap from > the Kubernetes environment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21165) Azure EventHub Emulator + camel Authentication issue
[ https://issues.apache.org/jira/browse/CAMEL-21165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879110#comment-17879110 ] Andrea Cosentino commented on CAMEL-21165: -- https://camel.apache.org/community/support/ > Azure EventHub Emulator + camel Authentication issue > - > > Key: CAMEL-21165 > URL: https://issues.apache.org/jira/browse/CAMEL-21165 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.7.0 >Reporter: Nilanjan Gogoi >Priority: Major > > Hi, > I am trying to connect to EventHub Emulator and Azurite storage blob > container emulator from my Springboot service which is using the latest Azure > SDK BOM(1.2.26) to support azure test containers and Apache Camel v4.7.0 > (primarily for Azure Endpoint route builder configurations). I am seeing 403 > Blob storage authentication failures due to signature mismatch. Could you > kindly suggest which version of Azure SDK bom and Apache Camel are compatible > for recent Emulators to unblock this issue ? Let me know if any more details > are needed from my end. > Below is the snippet from my error stacktrace: > Error occurred in partition processor for partition NONE, > com.azure.storage.blob.models.BlobStorageException: If you are using a > StorageSharedKeyCredential, and the server returned an error message that > says 'Signature did not match', you can compare the string to sign with the > one generated by the SDK > Below are the properties my application.yaml using azure event hub emulator > configurations > azure: > container-name: "static-container" > event-hub-connection-string: > "Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;" > inbound-event-hub-consumer-group: cg1 > inbound-event-hub-name: ev1 > namespace: emulatorns1 > outbound-event-hub-consumer-group: cg2 > outbound-event-hub-name: ev2 > storage-account-name: devstoreaccount1 > storage-connection-string: > "AccountName=devstoreaccount1;AccountKey=accountkey;DefaultEndpointsProtocol=http;BlobEndpoint=http://127.0.0.1:1/devstoreaccount1;"; > Thanks, > Nilanjan Gogoi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-21165) Azure EventHub Emulator + camel Authentication issue
[ https://issues.apache.org/jira/browse/CAMEL-21165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino closed CAMEL-21165. Resolution: Invalid > Azure EventHub Emulator + camel Authentication issue > - > > Key: CAMEL-21165 > URL: https://issues.apache.org/jira/browse/CAMEL-21165 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.7.0 >Reporter: Nilanjan Gogoi >Priority: Major > > Hi, > I am trying to connect to EventHub Emulator and Azurite storage blob > container emulator from my Springboot service which is using the latest Azure > SDK BOM(1.2.26) to support azure test containers and Apache Camel v4.7.0 > (primarily for Azure Endpoint route builder configurations). I am seeing 403 > Blob storage authentication failures due to signature mismatch. Could you > kindly suggest which version of Azure SDK bom and Apache Camel are compatible > for recent Emulators to unblock this issue ? Let me know if any more details > are needed from my end. > Below is the snippet from my error stacktrace: > Error occurred in partition processor for partition NONE, > com.azure.storage.blob.models.BlobStorageException: If you are using a > StorageSharedKeyCredential, and the server returned an error message that > says 'Signature did not match', you can compare the string to sign with the > one generated by the SDK > Below are the properties my application.yaml using azure event hub emulator > configurations > azure: > container-name: "static-container" > event-hub-connection-string: > "Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;" > inbound-event-hub-consumer-group: cg1 > inbound-event-hub-name: ev1 > namespace: emulatorns1 > outbound-event-hub-consumer-group: cg2 > outbound-event-hub-name: ev2 > storage-account-name: devstoreaccount1 > storage-connection-string: > "AccountName=devstoreaccount1;AccountKey=accountkey;DefaultEndpointsProtocol=http;BlobEndpoint=http://127.0.0.1:1/devstoreaccount1;"; > Thanks, > Nilanjan Gogoi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21165) Azure EventHub Emulator + camel Authentication issue
[ https://issues.apache.org/jira/browse/CAMEL-21165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879109#comment-17879109 ] Andrea Cosentino commented on CAMEL-21165: -- This is not a bug, this is more a discussion, please write to dev or users mailing list, or open a thread in Zulip. > Azure EventHub Emulator + camel Authentication issue > - > > Key: CAMEL-21165 > URL: https://issues.apache.org/jira/browse/CAMEL-21165 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.7.0 >Reporter: Nilanjan Gogoi >Priority: Major > > Hi, > I am trying to connect to EventHub Emulator and Azurite storage blob > container emulator from my Springboot service which is using the latest Azure > SDK BOM(1.2.26) to support azure test containers and Apache Camel v4.7.0 > (primarily for Azure Endpoint route builder configurations). I am seeing 403 > Blob storage authentication failures due to signature mismatch. Could you > kindly suggest which version of Azure SDK bom and Apache Camel are compatible > for recent Emulators to unblock this issue ? Let me know if any more details > are needed from my end. > Below is the snippet from my error stacktrace: > Error occurred in partition processor for partition NONE, > com.azure.storage.blob.models.BlobStorageException: If you are using a > StorageSharedKeyCredential, and the server returned an error message that > says 'Signature did not match', you can compare the string to sign with the > one generated by the SDK > Below are the properties my application.yaml using azure event hub emulator > configurations > azure: > container-name: "static-container" > event-hub-connection-string: > "Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;" > inbound-event-hub-consumer-group: cg1 > inbound-event-hub-name: ev1 > namespace: emulatorns1 > outbound-event-hub-consumer-group: cg2 > outbound-event-hub-name: ev2 > storage-account-name: devstoreaccount1 > storage-connection-string: > "AccountName=devstoreaccount1;AccountKey=accountkey;DefaultEndpointsProtocol=http;BlobEndpoint=http://127.0.0.1:1/devstoreaccount1;"; > Thanks, > Nilanjan Gogoi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21161) camel-aws2-s3 is uploading always files as multipart when multiPartUpload is set true
[
https://issues.apache.org/jira/browse/CAMEL-21161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878863#comment-17878863
]
Andrea Cosentino commented on CAMEL-21161:
--
Once it's fixed I'll merge this.
> camel-aws2-s3 is uploading always files as multipart when multiPartUpload is
> set true
> -
>
> Key: CAMEL-21161
> URL: https://issues.apache.org/jira/browse/CAMEL-21161
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
>Affects Versions: 4.7.0
>Reporter: Guillem Folch
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.8.0
>
> Attachments: CAMEL-21161.patch
>
>
> The Camel component camel-aws2-s3 has a producer boolean option called
> multiPartUpload.
> Based on the documentation, when this attribute is set to true, the upload
> will be with multipart format in case the file is larger than the partSize
> (another attribute).
> This is not happening, when multiPartUpload is set to true, the upload is
> always in multipart format unless the fileSize is 0, which is a corner case.
> The root cause of the problem is in the AWS2S3Producer code around line 151.
> _long partSize = getConfiguration().getPartSize();_
> _if (contentLength == 0 && contentLength < partSize) {_
> _// optimize to do a single op if content length is known and <
> part size_
> _LOG.debug("File size < partSize. Uploading file in single
> operation: {}", filePayload);_
> _processSingleOp(exchange);_
> _return;_
> _}_
> If the contentLength is not 0, the condition "{_}contentLength < partSize"{_}
> is never met so the upload is always done as multipart.
> This is really affecting performance upload when files are below the partSize.
> The proposed fix is just to change the condition to:
> _if (contentLength == 0 || contentLength < partSize) {_
> _..._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21161) camel-aws2-s3 is uploading always files as multipart when multiPartUpload is set true
[
https://issues.apache.org/jira/browse/CAMEL-21161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-21161:
Assignee: Andrea Cosentino
> camel-aws2-s3 is uploading always files as multipart when multiPartUpload is
> set true
> -
>
> Key: CAMEL-21161
> URL: https://issues.apache.org/jira/browse/CAMEL-21161
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
>Affects Versions: 4.7.0
>Reporter: Guillem Folch
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.8.0
>
> Attachments: CAMEL-21161.patch
>
>
> The Camel component camel-aws2-s3 has a producer boolean option called
> multiPartUpload.
> Based on the documentation, when this attribute is set to true, the upload
> will be with multipart format in case the file is larger than the partSize
> (another attribute).
> This is not happening, when multiPartUpload is set to true, the upload is
> always in multipart format unless the fileSize is 0, which is a corner case.
> The root cause of the problem is in the AWS2S3Producer code around line 151.
> _long partSize = getConfiguration().getPartSize();_
> _if (contentLength == 0 && contentLength < partSize) {_
> _// optimize to do a single op if content length is known and <
> part size_
> _LOG.debug("File size < partSize. Uploading file in single
> operation: {}", filePayload);_
> _processSingleOp(exchange);_
> _return;_
> _}_
> If the contentLength is not 0, the condition "{_}contentLength < partSize"{_}
> is never met so the upload is always done as multipart.
> This is really affecting performance upload when files are below the partSize.
> The proposed fix is just to change the condition to:
> _if (contentLength == 0 || contentLength < partSize) {_
> _..._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21142) Kubernetes Secrets/Configmap: Trigger context reloading on update
Andrea Cosentino created CAMEL-21142: Summary: Kubernetes Secrets/Configmap: Trigger context reloading on update Key: CAMEL-21142 URL: https://issues.apache.org/jira/browse/CAMEL-21142 Project: Camel Issue Type: New Feature Components: camel-kubernetes Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 We have already reload tasks in AWS, GCP and Azure Key Vault for triggering a context reload on particular events. The aim of this issue is to do the same in a cloud context, when we are using a particular secret or configmap from the Kubernetes environment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21142) Kubernetes Secrets/Configmap: Trigger context reloading on update
[ https://issues.apache.org/jira/browse/CAMEL-21142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21142: - Priority: Minor (was: Major) > Kubernetes Secrets/Configmap: Trigger context reloading on update > - > > Key: CAMEL-21142 > URL: https://issues.apache.org/jira/browse/CAMEL-21142 > Project: Camel > Issue Type: New Feature > Components: camel-kubernetes >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > > We have already reload tasks in AWS, GCP and Azure Key Vault for triggering a > context reload on particular events. The aim of this issue is to do the same > in a cloud context, when we are using a particular secret or configmap from > the Kubernetes environment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21116) Camel-AWS2-S3: Make ignoreBody supported also for getObject producer operation
[ https://issues.apache.org/jira/browse/CAMEL-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21116. -- Resolution: Fixed > Camel-AWS2-S3: Make ignoreBody supported also for getObject producer operation > -- > > Key: CAMEL-21116 > URL: https://issues.apache.org/jira/browse/CAMEL-21116 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21116) Camel-AWS2-S3: Make ignoreBody supported also for getObject producer operation
Andrea Cosentino created CAMEL-21116: Summary: Camel-AWS2-S3: Make ignoreBody supported also for getObject producer operation Key: CAMEL-21116 URL: https://issues.apache.org/jira/browse/CAMEL-21116 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21107) Camel-Kubernetes: Add ability to add annotation to create resources operation
Andrea Cosentino created CAMEL-21107: Summary: Camel-Kubernetes: Add ability to add annotation to create resources operation Key: CAMEL-21107 URL: https://issues.apache.org/jira/browse/CAMEL-21107 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21105) Camel-Kubernetes: Configmap creation should allow to add annotations
[ https://issues.apache.org/jira/browse/CAMEL-21105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21105. -- Resolution: Fixed > Camel-Kubernetes: Configmap creation should allow to add annotations > > > Key: CAMEL-21105 > URL: https://issues.apache.org/jira/browse/CAMEL-21105 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21105) Camel-Kubernetes: Configmap creation should allow to add annotations
Andrea Cosentino created CAMEL-21105: Summary: Camel-Kubernetes: Configmap creation should allow to add annotations Key: CAMEL-21105 URL: https://issues.apache.org/jira/browse/CAMEL-21105 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21101) Camel-Hashicorp-Vault: Get Secret operation doesn't take into account the secretPath configuration parameter
[ https://issues.apache.org/jira/browse/CAMEL-21101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21101. -- Resolution: Fixed > Camel-Hashicorp-Vault: Get Secret operation doesn't take into account the > secretPath configuration parameter > > > Key: CAMEL-21101 > URL: https://issues.apache.org/jira/browse/CAMEL-21101 > Project: Camel > Issue Type: Bug >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.4, 4.8.0 > > > Only the header. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21101) Camel-Hashicorp-Vault: Get Secret operation doesn't take into account the secretPath configuration parameter
Andrea Cosentino created CAMEL-21101: Summary: Camel-Hashicorp-Vault: Get Secret operation doesn't take into account the secretPath configuration parameter Key: CAMEL-21101 URL: https://issues.apache.org/jira/browse/CAMEL-21101 Project: Camel Issue Type: Bug Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.4, 4.8.0 Only the header. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21062) Azure Key Vault Properties function: Add documentation about creating required infra
[ https://issues.apache.org/jira/browse/CAMEL-21062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21062: - Fix Version/s: 4.8.0 (was: 4.x) > Azure Key Vault Properties function: Add documentation about creating > required infra > > > Key: CAMEL-21062 > URL: https://issues.apache.org/jira/browse/CAMEL-21062 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21062) Azure Key Vault Properties function: Add documentation about creating required infra
[ https://issues.apache.org/jira/browse/CAMEL-21062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21062. -- Resolution: Fixed > Azure Key Vault Properties function: Add documentation about creating > required infra > > > Key: CAMEL-21062 > URL: https://issues.apache.org/jira/browse/CAMEL-21062 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21061) Google Secrets Manager Properties function: Add documentation about creating required infra
[ https://issues.apache.org/jira/browse/CAMEL-21061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21061. -- Resolution: Fixed > Google Secrets Manager Properties function: Add documentation about creating > required infra > --- > > Key: CAMEL-21061 > URL: https://issues.apache.org/jira/browse/CAMEL-21061 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21061) Google Secrets Manager Properties function: Add documentation about creating required infra
[ https://issues.apache.org/jira/browse/CAMEL-21061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21061: - Fix Version/s: 4.8.0 (was: 4.x) > Google Secrets Manager Properties function: Add documentation about creating > required infra > --- > > Key: CAMEL-21061 > URL: https://issues.apache.org/jira/browse/CAMEL-21061 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21060) AWS Secrets Manager Properties function: Add documentation about creating required infra
[ https://issues.apache.org/jira/browse/CAMEL-21060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874821#comment-17874821 ] Andrea Cosentino commented on CAMEL-21060: -- Already done. > AWS Secrets Manager Properties function: Add documentation about creating > required infra > > > Key: CAMEL-21060 > URL: https://issues.apache.org/jira/browse/CAMEL-21060 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21060) AWS Secrets Manager Properties function: Add documentation about creating required infra
[ https://issues.apache.org/jira/browse/CAMEL-21060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21060. -- Resolution: Fixed > AWS Secrets Manager Properties function: Add documentation about creating > required infra > > > Key: CAMEL-21060 > URL: https://issues.apache.org/jira/browse/CAMEL-21060 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21060) AWS Secrets Manager Properties function: Add documentation about creating required infra
[ https://issues.apache.org/jira/browse/CAMEL-21060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21060: - Fix Version/s: 4.8.0 (was: 4.x) > AWS Secrets Manager Properties function: Add documentation about creating > required infra > > > Key: CAMEL-21060 > URL: https://issues.apache.org/jira/browse/CAMEL-21060 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21061) Google Secrets Manager Properties function: Add documentation about creating required infra
Andrea Cosentino created CAMEL-21061: Summary: Google Secrets Manager Properties function: Add documentation about creating required infra Key: CAMEL-21061 URL: https://issues.apache.org/jira/browse/CAMEL-21061 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21062) Azure Key Vault Properties function: Add documentation about creating required infra
Andrea Cosentino created CAMEL-21062: Summary: Azure Key Vault Properties function: Add documentation about creating required infra Key: CAMEL-21062 URL: https://issues.apache.org/jira/browse/CAMEL-21062 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21060) AWS Secrets Manager Properties function: Add documentation about creating required infra
Andrea Cosentino created CAMEL-21060: Summary: AWS Secrets Manager Properties function: Add documentation about creating required infra Key: CAMEL-21060 URL: https://issues.apache.org/jira/browse/CAMEL-21060 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21010) camel-milvus: collection name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21010.
--
Resolution: Information Provided
> camel-milvus: collection name mismatch with embeddings
> --
>
> Key: CAMEL-21010
> URL: https://issues.apache.org/jira/browse/CAMEL-21010
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling collection names.
> The embedding component requires the collection name to be specified as a
> header, while the Milvus component allows for a different collection name to
> be used.
> For instance:
> {code:java}
>
>MyTestCollectionName2
>
>
>
> {code}
> This inconsistency can lead to confusion and errors when trying to use both
> components together. It would be beneficial to standardize the behavior of
> these components so that they can work seamlessly with each other.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21010) camel-milvus: collection name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871644#comment-17871644
]
Andrea Cosentino commented on CAMEL-21010:
--
There is no easy way of doing this because the library works differently in
relation to Qdrant. We need to specify the collectionName at POJO level when
doing insert/upsert. This means we have to pass it via an header. I think we
should document this in the component doc.
> camel-milvus: collection name mismatch with embeddings
> --
>
> Key: CAMEL-21010
> URL: https://issues.apache.org/jira/browse/CAMEL-21010
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling collection names.
> The embedding component requires the collection name to be specified as a
> header, while the Milvus component allows for a different collection name to
> be used.
> For instance:
> {code:java}
>
>MyTestCollectionName2
>
>
>
> {code}
> This inconsistency can lead to confusion and errors when trying to use both
> components together. It would be beneficial to standardize the behavior of
> these components so that they can work seamlessly with each other.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21012) camel-milvus: action name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21012.
--
Resolution: Fixed
> camel-milvus: action name mismatch with embeddings
> --
>
> Key: CAMEL-21012
> URL: https://issues.apache.org/jira/browse/CAMEL-21012
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling actions
> The embedding component requires the action name to be specified as a header:
> {code:xml}
>
> UPSERT
>
> {code}
> However, this causes problems when using in combination with the Milvus
> embedding, because the transformer creates a InsertParam object.
> The problem is in the `private void upsert(Exchange exchange)` method from
> MilvusProducer.java. When we try to get the body of the message, we look for
> an `UpsertParam.class`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21023) Camel-Spring-Boot: Add Langchain component starters Integration tests
[ https://issues.apache.org/jira/browse/CAMEL-21023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21023. -- Resolution: Fixed > Camel-Spring-Boot: Add Langchain component starters Integration tests > - > > Key: CAMEL-21023 > URL: https://issues.apache.org/jira/browse/CAMEL-21023 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > They're missing in the set. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21037) Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-21037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21037: - Description: I guess this needs to be addressed. By following the documentation, deploying on OCP doesn't work with the current POM template. (was: I guess this needs to be addressed. By testing following the documentation, deploying on OCP doesn't work with the current POM template.) > Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target > we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin > -- > > Key: CAMEL-21037 > URL: https://issues.apache.org/jira/browse/CAMEL-21037 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.x > > > I guess this needs to be addressed. By following the documentation, deploying > on OCP doesn't work with the current POM template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21037) Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-21037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869897#comment-17869897 ] Andrea Cosentino commented on CAMEL-21037: -- [~tdiesler] I assigned this to you, because you worked on the feature. Let me know if you have time. > Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target > we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin > -- > > Key: CAMEL-21037 > URL: https://issues.apache.org/jira/browse/CAMEL-21037 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.x > > > I guess this needs to be addressed. By testing following the documentation, > deploying on OCP doesn't work with the current POM template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21037) Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin
Andrea Cosentino created CAMEL-21037: Summary: Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin Key: CAMEL-21037 URL: https://issues.apache.org/jira/browse/CAMEL-21037 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Thomas Diesler Fix For: 4.x I guess this needs to be addressed. By testing following the documentation, deploying on OCP doesn't work with the current POM template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21021) Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead of pure Cloudtrail
[ https://issues.apache.org/jira/browse/CAMEL-21021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21021. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on > Secrets update by using Eventbridge service instead of pure Cloudtrail > --- > > Key: CAMEL-21021 > URL: https://issues.apache.org/jira/browse/CAMEL-21021 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > Eventbridge could send events to SQS or SNS, we can choose SQS for > convenience as default. It's far more reliable than waiting for events > publish on Cloudtrail and we could be able to refresh the context faster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
