[jira] [Updated] (CAMEL-18064) Cannot set server side encryption SSE-S3 for S3 bucket

[ https://issues.apache.org/jira/browse/CAMEL-18064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18064: - Fix Version/s: 3.17.0 > Cannot set server side encryption SSE-S3 for S3 bucket > ---

[jira] [Resolved] (CAMEL-18064) Cannot set server side encryption SSE-S3 for S3 bucket

[ https://issues.apache.org/jira/browse/CAMEL-18064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18064. -- Resolution: Fixed > Cannot set server side encryption SSE-S3 for S3 bucket > -

[jira] [Assigned] (CAMEL-18064) Cannot set server side encryption SSE-S3 for S3 bucket

[ https://issues.apache.org/jira/browse/CAMEL-18064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18064: Assignee: Andrea Cosentino > Cannot set server side encryption SSE-S3 for S3 buck

[jira] [Work started] (CAMEL-18030) camel-jclouds - Upgrade to 2.5.x

[ https://issues.apache.org/jira/browse/CAMEL-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18030 started by Andrea Cosentino. > camel-jclouds - Upgrade to 2.5.x > >

[jira] [Assigned] (CAMEL-18030) camel-jclouds - Upgrade to 2.5.x

[ https://issues.apache.org/jira/browse/CAMEL-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18030: Assignee: Andrea Cosentino > camel-jclouds - Upgrade to 2.5.x > -

[jira] [Resolved] (CAMEL-18030) camel-jclouds - Upgrade to 2.5.x

[ https://issues.apache.org/jira/browse/CAMEL-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18030. -- Resolution: Fixed > camel-jclouds - Upgrade to 2.5.x > ---

[jira] [Updated] (CAMEL-18030) camel-jclouds - Upgrade to 2.5.x

[ https://issues.apache.org/jira/browse/CAMEL-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18030: - Fix Version/s: 3.17.0 (was: 3.x) > camel-jclouds - Upgrade to 2.5

[jira] [Work stopped] (CAMEL-18030) camel-jclouds - Upgrade to 2.5.x

[ https://issues.apache.org/jira/browse/CAMEL-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18030 stopped by Andrea Cosentino. > camel-jclouds - Upgrade to 2.5.x > >

[jira] [Resolved] (CAMEL-18033) camel-kamelet - Debezium Source Component

[ https://issues.apache.org/jira/browse/CAMEL-18033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18033. -- Resolution: Invalid Please open the issue at Camel-kamelets issues tracker on github

[jira] [Commented] (CAMEL-18022) camel-aws - Head Bucket Request Fails when route is configured to folders in Bucket

[ https://issues.apache.org/jira/browse/CAMEL-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529068#comment-17529068 ] Andrea Cosentino commented on CAMEL-18022: -- I'll check, but bucket name is a th

[jira] [Commented] (CAMEL-18022) camel-aws - Head Bucket Request Fails when route is configured to folders in Bucket

[ https://issues.apache.org/jira/browse/CAMEL-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529051#comment-17529051 ] Andrea Cosentino commented on CAMEL-18022: -- In that case the bucket name is onl

[jira] [Commented] (CAMEL-18022) camel-aws - Head Bucket Request Fails when route is configured to folders in Bucket

[ https://issues.apache.org/jira/browse/CAMEL-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529030#comment-17529030 ] Andrea Cosentino commented on CAMEL-18022: -- Head bucket is a cheaper and faster

[jira] [Assigned] (CAMEL-18022) camel-aws - HeadObject Request Fails when route is configured to folders in Bucket

[ https://issues.apache.org/jira/browse/CAMEL-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18022: Assignee: Andrea Cosentino > camel-aws - HeadObject Request Fails when route is c

[jira] [Commented] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525430#comment-17525430 ] Andrea Cosentino commented on CAMEL-16287: -- We should start a release in a coup

[jira] [Updated] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-16287: - Fix Version/s: 3.11.7 > camel-aws2-sqs should use pagination for deciding which aws sqs

[jira] [Commented] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525097#comment-17525097 ] Andrea Cosentino commented on CAMEL-16287: -- For the moment I've added the 1000

[jira] [Resolved] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-16287. -- Resolution: Fixed > camel-aws2-sqs should use pagination for deciding which aws sqs qu

[jira] [Commented] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525038#comment-17525038 ] Andrea Cosentino commented on CAMEL-16287: -- Btw I'll have a look for sure. Than

[jira] [Commented] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525037#comment-17525037 ] Andrea Cosentino commented on CAMEL-16287: -- I don't quite getting the problem.

[jira] [Commented] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525016#comment-17525016 ] Andrea Cosentino commented on CAMEL-16287: -- I'll have a look > camel-aws2-sqs

[jira] [Updated] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-16287: - Fix Version/s: 3.14.3 3.17.0 (was: 3.10.0) > c

[jira] [Reopened] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create

[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reopened CAMEL-16287: -- > camel-aws2-sqs should use pagination for deciding which aws sqs queues it > should crea

[jira] [Commented] (CAMEL-17423) Google Pubsub Authentication

[ https://issues.apache.org/jira/browse/CAMEL-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522292#comment-17522292 ] Andrea Cosentino commented on CAMEL-17423: -- It makes sense totally, please rais

[jira] [Resolved] (CAMEL-17958) upgrade testcontainers to 1.17.x

[ https://issues.apache.org/jira/browse/CAMEL-17958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17958. -- Resolution: Fixed > upgrade testcontainers to 1.17.x > ---

[jira] [Assigned] (CAMEL-17958) upgrade testcontainers to 1.17.x

[ https://issues.apache.org/jira/browse/CAMEL-17958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-17958: Assignee: Andrea Cosentino > upgrade testcontainers to 1.17.x > -

[jira] [Commented] (CAMEL-17093) Debezium 1.7.0 - Vitess Connector

[ https://issues.apache.org/jira/browse/CAMEL-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521445#comment-17521445 ] Andrea Cosentino commented on CAMEL-17093: -- No, I didn't start. Just assigned t

[jira] [Assigned] (CAMEL-17093) Debezium 1.7.0 - Vitess Connector

[ https://issues.apache.org/jira/browse/CAMEL-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-17093: Assignee: Ramu (was: Andrea Cosentino) > Debezium 1.7.0 - Vitess Connector > ---

[jira] [Resolved] (CAMEL-17686) Support ability to load properties from Vault/Secrets cloud services - Azure Key Vault

[ https://issues.apache.org/jira/browse/CAMEL-17686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17686. -- Resolution: Fixed > Support ability to load properties from Vault/Secrets cloud servic

[jira] [Updated] (CAMEL-17686) Support ability to load properties from Vault/Secrets cloud services - Azure Key Vault

[ https://issues.apache.org/jira/browse/CAMEL-17686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17686: - Fix Version/s: 3.17.0 (was: 3.x) > Support ability to load proper

[jira] [Commented] (CAMEL-17686) Support ability to load properties from Vault/Secrets cloud services - Azure Key Vault

[ https://issues.apache.org/jira/browse/CAMEL-17686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515900#comment-17515900 ] Andrea Cosentino commented on CAMEL-17686: -- Done for Plain camel. Missing Camel

[jira] [Resolved] (CAMEL-17687) Create a Camel Azure Key Vault component

[ https://issues.apache.org/jira/browse/CAMEL-17687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17687. -- Resolution: Fixed > Create a Camel Azure Key Vault component > ---

[jira] [Commented] (CAMEL-17888) Dependent component spring-beans is affected by the Spring Framework vulnerability CVE-2010-1622

[ https://issues.apache.org/jira/browse/CAMEL-17888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515277#comment-17515277 ] Andrea Cosentino commented on CAMEL-17888: -- Also this is not really the way of

[jira] [Commented] (CAMEL-17888) Dependent component spring-beans is affected by the Spring Framework vulnerability CVE-2010-1622

[ https://issues.apache.org/jira/browse/CAMEL-17888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515271#comment-17515271 ] Andrea Cosentino commented on CAMEL-17888: -- Without the information about affec

[jira] [Assigned] (CAMEL-17884) Guava is overriden to an older version in bigquery starter

[ https://issues.apache.org/jira/browse/CAMEL-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-17884: Assignee: Andrea Cosentino > Guava is overriden to an older version in bigquery s

[jira] [Resolved] (CAMEL-17884) Guava is overriden to an older version in bigquery starter

[ https://issues.apache.org/jira/browse/CAMEL-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17884. -- Resolution: Fixed > Guava is overriden to an older version in bigquery starter > -

[jira] [Updated] (CAMEL-17884) Guava is overriden to an older version in bigquery starter

[ https://issues.apache.org/jira/browse/CAMEL-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17884: - Fix Version/s: 3.17.0 > Guava is overriden to an older version in bigquery starter > ---

[jira] [Updated] (CAMEL-17884) Guava is overriden to an older version in bigquery starter

[ https://issues.apache.org/jira/browse/CAMEL-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17884: - Affects Version/s: (was: 3.17.0) > Guava is overriden to an older version in bigquer

[jira] [Resolved] (CAMEL-17882) Camel-Spring-Boot: Create a Camel Azure Key Vault component starter

[ https://issues.apache.org/jira/browse/CAMEL-17882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17882. -- Resolution: Fixed > Camel-Spring-Boot: Create a Camel Azure Key Vault component starte

[jira] [Commented] (CAMEL-17687) Create a Camel Azure Key Vault component

[ https://issues.apache.org/jira/browse/CAMEL-17687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514780#comment-17514780 ] Andrea Cosentino commented on CAMEL-17687: -- Need to update the documentation >

[jira] [Commented] (CAMEL-17687) Create a Camel Azure Key Vault component

[ https://issues.apache.org/jira/browse/CAMEL-17687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514779#comment-17514779 ] Andrea Cosentino commented on CAMEL-17687: -- Following operations are supported

[jira] [Created] (CAMEL-17882) Camel-Spring-Boot: Create a Camel Azure Key Vault component starter

Andrea Cosentino created CAMEL-17882: Summary: Camel-Spring-Boot: Create a Camel Azure Key Vault component starter Key: CAMEL-17882 URL: https://issues.apache.org/jira/browse/CAMEL-17882 Project:

[jira] [Commented] (CAMEL-17881) TLS for MLLP Component

[ https://issues.apache.org/jira/browse/CAMEL-17881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514725#comment-17514725 ] Andrea Cosentino commented on CAMEL-17881: -- [~hqstevenson] did you have some ti

[jira] [Commented] (CAMEL-17687) Create a Camel Azure Key Vault component

[ https://issues.apache.org/jira/browse/CAMEL-17687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514681#comment-17514681 ] Andrea Cosentino commented on CAMEL-17687: -- First iteration done. > Create a C

[jira] [Updated] (CAMEL-17687) Create a Camel Azure Key Vault component

[ https://issues.apache.org/jira/browse/CAMEL-17687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17687: - Fix Version/s: 3.17.0 (was: 3.x) > Create a Camel Azure Key Vault

[jira] [Resolved] (CAMEL-17854) Camel-AWS-SNS: support byte arrays when mapping camel headers to sns attribute

[ https://issues.apache.org/jira/browse/CAMEL-17854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17854. -- Resolution: Fixed > Camel-AWS-SNS: support byte arrays when mapping camel headers to s

[jira] [Created] (CAMEL-17854) Camel-AWS-SNS: support byte arrays when mapping camel headers to sns attribute

Andrea Cosentino created CAMEL-17854: Summary: Camel-AWS-SNS: support byte arrays when mapping camel headers to sns attribute Key: CAMEL-17854 URL: https://issues.apache.org/jira/browse/CAMEL-17854

[jira] [Resolved] (CAMEL-17816) aws2-sqs: support byte arrays when mapping camel headers to sqs attribute

[ https://issues.apache.org/jira/browse/CAMEL-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17816. -- Resolution: Fixed > aws2-sqs: support byte arrays when mapping camel headers to sqs at

[jira] [Updated] (CAMEL-17816) aws2-sqs: support byte arrays when mapping camel headers to sqs attribute

[ https://issues.apache.org/jira/browse/CAMEL-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17816: - Fix Version/s: 3.17.0 > aws2-sqs: support byte arrays when mapping camel headers to sqs

[jira] [Updated] (CAMEL-17816) aws2-sqs: support byte arrays when mapping camel headers to sqs attribute

[ https://issues.apache.org/jira/browse/CAMEL-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17816: - Summary: aws2-sqs: support byte arrays when mapping camel headers to sqs attribute (was

[jira] [Resolved] (CAMEL-17828) Remove Camel-MongoDB features from Camel-Karaf

[ https://issues.apache.org/jira/browse/CAMEL-17828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17828. -- Resolution: Fixed > Remove Camel-MongoDB features from Camel-Karaf > -

[jira] [Resolved] (CAMEL-17827) Upgrade to MongoDB Driver Core 4.5.0

[ https://issues.apache.org/jira/browse/CAMEL-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17827. -- Resolution: Fixed > Upgrade to MongoDB Driver Core 4.5.0 > ---

[jira] [Updated] (CAMEL-17828) Remove Camel-MongoDB features from Camel-Karaf

[ https://issues.apache.org/jira/browse/CAMEL-17828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17828: - Fix Version/s: 3.16.0 > Remove Camel-MongoDB features from Camel-Karaf > ---

[jira] [Updated] (CAMEL-17827) Upgrade to MongoDB Driver Core 4.5.0

[ https://issues.apache.org/jira/browse/CAMEL-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17827: - Fix Version/s: 3.16.0 > Upgrade to MongoDB Driver Core 4.5.0 > -

[jira] [Created] (CAMEL-17828) Remove Camel-MongoDB features from Camel-Karaf

Andrea Cosentino created CAMEL-17828: Summary: Remove Camel-MongoDB features from Camel-Karaf Key: CAMEL-17828 URL: https://issues.apache.org/jira/browse/CAMEL-17828 Project: Camel Issue

[jira] [Created] (CAMEL-17827) Upgrade to MongoDB Driver Core 4.5.0

Andrea Cosentino created CAMEL-17827: Summary: Upgrade to MongoDB Driver Core 4.5.0 Key: CAMEL-17827 URL: https://issues.apache.org/jira/browse/CAMEL-17827 Project: Camel Issue Type: Task

[jira] [Resolved] (CAMEL-17801) add tests in camel-mongodb-starter

[ https://issues.apache.org/jira/browse/CAMEL-17801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17801. -- Resolution: Fixed > add tests in camel-mongodb-starter > -

[jira] [Updated] (CAMEL-17801) add tests in camel-mongodb-starter

[ https://issues.apache.org/jira/browse/CAMEL-17801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17801: - Fix Version/s: 3.16.0 > add tests in camel-mongodb-starter > ---

[jira] [Resolved] (CAMEL-17786) No sources for camel-k 1.8.1 and 1.8.2

[ https://issues.apache.org/jira/browse/CAMEL-17786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17786. -- Resolution: Fixed > No sources for camel-k 1.8.1 and 1.8.2 > -

[jira] [Commented] (CAMEL-17786) No sources for camel-k 1.8.1 and 1.8.2

[ https://issues.apache.org/jira/browse/CAMEL-17786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506002#comment-17506002 ] Andrea Cosentino commented on CAMEL-17786: -- https://dist.apache.org/repos/dist/

[jira] [Commented] (CAMEL-17786) No sources for camel-k 1.8.1 and 1.8.2

[ https://issues.apache.org/jira/browse/CAMEL-17786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505997#comment-17505997 ] Andrea Cosentino commented on CAMEL-17786: -- The sources for this ticket have be

[jira] [Resolved] (CAMEL-17786) No sources for camel-k 1.8.1 and 1.8.2

[ https://issues.apache.org/jira/browse/CAMEL-17786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17786. -- Resolution: Fixed > No sources for camel-k 1.8.1 and 1.8.2 > -

[jira] [Commented] (CAMEL-17786) No sources for camel-k 1.8.1 and 1.8.2

[ https://issues.apache.org/jira/browse/CAMEL-17786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505273#comment-17505273 ] Andrea Cosentino commented on CAMEL-17786: -- The source is available in GitHub t

[jira] [Commented] (CAMEL-17786) No sources for camel-k 1.8.1 and 1.8.2

[ https://issues.apache.org/jira/browse/CAMEL-17786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505268#comment-17505268 ] Andrea Cosentino commented on CAMEL-17786: -- Forgot to upload. I'll do > No sou

[jira] [Updated] (CAMEL-17786) No sources for camel-k 1.8.1 and 1.8.2

[ https://issues.apache.org/jira/browse/CAMEL-17786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17786: - Priority: Major (was: Critical) > No sources for camel-k 1.8.1 and 1.8.2 >

[jira] [Assigned] (CAMEL-17786) No sources for camel-k 1.8.1 and 1.8.2

[ https://issues.apache.org/jira/browse/CAMEL-17786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-17786: Assignee: Andrea Cosentino > No sources for camel-k 1.8.1 and 1.8.2 > ---

[jira] [Updated] (CAMEL-17769) AWS Kinesis: Make the consumer set only the raw data on the body, and enrich the exchange with more header

[ https://issues.apache.org/jira/browse/CAMEL-17769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17769: - Fix Version/s: 3.16.0 (was: 3.17.0) > AWS Kinesis: Make the consu

[jira] [Resolved] (CAMEL-17769) AWS Kinesis: Make the consumer set only the raw data on the body, and enrich the exchange with more header

[ https://issues.apache.org/jira/browse/CAMEL-17769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17769. -- Resolution: Fixed > AWS Kinesis: Make the consumer set only the raw data on the body,

[jira] [Created] (CAMEL-17769) AWS Kinesis: Make the consumer set only the raw data on the body, and enrich the exchange with more header

Andrea Cosentino created CAMEL-17769: Summary: AWS Kinesis: Make the consumer set only the raw data on the body, and enrich the exchange with more header Key: CAMEL-17769 URL: https://issues.apache.org/jira/br

[jira] [Reopened] (CAMEL-17765) camel-quarkus-openapi-java not marking required boolean properties if variable prefixed with is

[ https://issues.apache.org/jira/browse/CAMEL-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reopened CAMEL-17765: -- > camel-quarkus-openapi-java not marking required boolean properties if > variable prefix

[jira] [Commented] (CAMEL-17765) camel-quarkus-openapi-java not marking required boolean properties if variable prefixed with is

[ https://issues.apache.org/jira/browse/CAMEL-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503078#comment-17503078 ] Andrea Cosentino commented on CAMEL-17765: -- https://github.com/apache/camel-qua

[jira] [Commented] (CAMEL-17765) camel-quarkus-openapi-java not marking required boolean properties if variable prefixed with is

[ https://issues.apache.org/jira/browse/CAMEL-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503074#comment-17503074 ] Andrea Cosentino commented on CAMEL-17765: -- Yes, but if you notice that using c

[jira] [Comment Edited] (CAMEL-17765) camel-quarkus-openapi-java not marking required boolean properties if variable prefixed with is

[ https://issues.apache.org/jira/browse/CAMEL-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503074#comment-17503074 ] Andrea Cosentino edited comment on CAMEL-17765 at 3/8/22, 5:36 PM: ---

[jira] [Resolved] (CAMEL-17765) camel-quarkus-openapi-java not marking required boolean properties if variable prefixed with is

[ https://issues.apache.org/jira/browse/CAMEL-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17765. -- Resolution: Invalid If it is a camel-quarkus bug, please open it here: https://github.

[jira] [Updated] (CAMEL-17368) camel-google-functions - Support GKE's workload identity

[ https://issues.apache.org/jira/browse/CAMEL-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17368: - Fix Version/s: 3.17.0 (was: 3.16.0) > camel-google-functions - Su

[jira] [Updated] (CAMEL-17369) Camel-google-storage - Support GKE's workload identity

[ https://issues.apache.org/jira/browse/CAMEL-17369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17369: - Fix Version/s: 3.17.0 (was: 3.16.0) > Camel-google-storage - Supp

[jira] [Updated] (CAMEL-17644) Support ability to load properties from Vault/Secrets cloud services

[ https://issues.apache.org/jira/browse/CAMEL-17644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17644: - Fix Version/s: 3.17.0 (was: 3.16.0) > Support ability to load pro

[jira] [Updated] (CAMEL-17339) Avoid List as configuration parameter types in Endpoint configurations

[ https://issues.apache.org/jira/browse/CAMEL-17339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17339: - Fix Version/s: 3.17.0 (was: 3.16.0) > Avoid List as configuration

[jira] [Commented] (CAMEL-17593) camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any info

[ https://issues.apache.org/jira/browse/CAMEL-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502457#comment-17502457 ] Andrea Cosentino commented on CAMEL-17593: -- Feel free to work on this one, I'd

[jira] [Commented] (CAMEL-17593) camel-aws2-sqs - Camel skips messageAttributes if more then 10 without any info

[ https://issues.apache.org/jira/browse/CAMEL-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502455#comment-17502455 ] Andrea Cosentino commented on CAMEL-17593: -- Yes [~davsclaus], it's an hard limi

[jira] [Resolved] (CAMEL-17739) Camel Google Secret Manager Properties Source: Support the usage of client default instance

[ https://issues.apache.org/jira/browse/CAMEL-17739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17739. -- Resolution: Fixed > Camel Google Secret Manager Properties Source: Support the usage o

[jira] [Commented] (CAMEL-17739) Camel Google Secret Manager Properties Source: Support the usage of client default instance

[ https://issues.apache.org/jira/browse/CAMEL-17739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501206#comment-17501206 ] Andrea Cosentino commented on CAMEL-17739: -- Done. Need to add documentation. >

[jira] [Commented] (CAMEL-16263) camel-google-pubsub - Consumer does not recover from 500 series error from Google

[ https://issues.apache.org/jira/browse/CAMEL-16263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500946#comment-17500946 ] Andrea Cosentino commented on CAMEL-16263: -- This has been fixed a long time ago

[jira] [Created] (CAMEL-17739) Camel Google Secret Manager Properties Source: Support the usage of client default instance

Andrea Cosentino created CAMEL-17739: Summary: Camel Google Secret Manager Properties Source: Support the usage of client default instance Key: CAMEL-17739 URL: https://issues.apache.org/jira/browse/CAMEL-1773

[jira] [Resolved] (CAMEL-17737) camel-salesforce consumer: message id not in sequence for platform events

[ https://issues.apache.org/jira/browse/CAMEL-17737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17737. -- Resolution: Invalid Please open the issue only on camel-kafka-connector issues for ca

[jira] [Assigned] (CAMEL-17652) camel-minio - Auto create bucket should not be done in endpoint

[ https://issues.apache.org/jira/browse/CAMEL-17652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-17652: Assignee: Andrea Cosentino > camel-minio - Auto create bucket should not be done

[jira] [Resolved] (CAMEL-17732) Secrets Manager Properties Sources: if default value is provided, we should not fail with wrong credentials

[ https://issues.apache.org/jira/browse/CAMEL-17732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17732. -- Resolution: Fixed > Secrets Manager Properties Sources: if default value is provided,

[jira] [Commented] (CAMEL-17730) Camel-AWS Secret Manager Properties Source: if the subkey contains a default value the actual won't substitute correctly the secret

[ https://issues.apache.org/jira/browse/CAMEL-17730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499934#comment-17499934 ] Andrea Cosentino commented on CAMEL-17730: -- Created CAMEL-17732 > Camel-AWS Se

[jira] [Created] (CAMEL-17732) Secrets Manager Properties Sources: if default value is provided, we should not fail with wrong credentials

Andrea Cosentino created CAMEL-17732: Summary: Secrets Manager Properties Sources: if default value is provided, we should not fail with wrong credentials Key: CAMEL-17732 URL: https://issues.apache.org/jira/b

[jira] [Commented] (CAMEL-17730) Camel-AWS Secret Manager Properties Source: if the subkey contains a default value the actual won't substitute correctly the secret

[ https://issues.apache.org/jira/browse/CAMEL-17730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499927#comment-17499927 ] Andrea Cosentino commented on CAMEL-17730: -- The behavior describe has been fixe

[jira] [Resolved] (CAMEL-17730) Camel-AWS Secret Manager Properties Source: if the subkey contains a default value the actual won't substitute correctly the secret

[ https://issues.apache.org/jira/browse/CAMEL-17730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17730. -- Resolution: Fixed > Camel-AWS Secret Manager Properties Source: if the subkey contains

[jira] [Created] (CAMEL-17730) Camel-AWS Secret Manager Properties Source: if the subkey contains a default value the actual won't substitute correctly the secret

Andrea Cosentino created CAMEL-17730: Summary: Camel-AWS Secret Manager Properties Source: if the subkey contains a default value the actual won't substitute correctly the secret Key: CAMEL-17730 URL: https://

[jira] [Commented] (CAMEL-17644) Support ability to load properties from Vault/Secrets cloud services

[ https://issues.apache.org/jira/browse/CAMEL-17644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499684#comment-17499684 ] Andrea Cosentino commented on CAMEL-17644: -- GCP Secret Manager - Done. > Suppo

[jira] [Resolved] (CAMEL-17684) Support ability to load properties from Vault/Secrets cloud services - GCP Secrets Manager

[ https://issues.apache.org/jira/browse/CAMEL-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17684. -- Resolution: Fixed > Support ability to load properties from Vault/Secrets cloud servic

[jira] [Commented] (CAMEL-17684) Support ability to load properties from Vault/Secrets cloud services - GCP Secrets Manager

[ https://issues.apache.org/jira/browse/CAMEL-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499677#comment-17499677 ] Andrea Cosentino commented on CAMEL-17684: -- Spring Boot support done. > Suppor

[jira] [Commented] (CAMEL-17684) Support ability to load properties from Vault/Secrets cloud services - GCP Secrets Manager

[ https://issues.apache.org/jira/browse/CAMEL-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499660#comment-17499660 ] Andrea Cosentino commented on CAMEL-17684: -- Only Spring Boot support is missing

[jira] [Commented] (CAMEL-17684) Support ability to load properties from Vault/Secrets cloud services - GCP Secrets Manager

[ https://issues.apache.org/jira/browse/CAMEL-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499555#comment-17499555 ] Andrea Cosentino commented on CAMEL-17684: -- This is done, need to add documenta

[jira] [Updated] (CAMEL-17684) Support ability to load properties from Vault/Secrets cloud services - GCP Secrets Manager

[ https://issues.apache.org/jira/browse/CAMEL-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17684: - Fix Version/s: 3.16.0 (was: 3.x) > Support ability to load proper

[jira] [Updated] (CAMEL-17713) CAMEL-AWS2-S3 doesn't support uploading files with custom metadata headers

[ https://issues.apache.org/jira/browse/CAMEL-17713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17713: - Fix Version/s: 3.14.2 3.11.6 3.16.0 > CAMEL-AWS2-S

[jira] [Resolved] (CAMEL-17713) CAMEL-AWS2-S3 doesn't support uploading files with custom metadata headers

[ https://issues.apache.org/jira/browse/CAMEL-17713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17713. -- Resolution: Fixed > CAMEL-AWS2-S3 doesn't support uploading files with custom metadata

[jira] [Commented] (CAMEL-17713) CAMEL-AWS2-S3 doesn't support uploading files with custom metadata headers

[ https://issues.apache.org/jira/browse/CAMEL-17713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498092#comment-17498092 ] Andrea Cosentino commented on CAMEL-17713: -- I don't think adding a way to add a

<    8   9   10   11   12   13   14   15   16   17   >