[jira] [Resolved] (CAMEL-21647) Create a jenkins job for Camel JBang IT test suite
[ https://issues.apache.org/jira/browse/CAMEL-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21647. -- Resolution: Fixed > Create a jenkins job for Camel JBang IT test suite > -- > > Key: CAMEL-21647 > URL: https://issues.apache.org/jira/browse/CAMEL-21647 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Federico Mariani >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > > The [Camel JBang > IT|https://github.com/apache/camel/tree/main/dsl/camel-jbang/camel-jbang-it] > test suite is slow to execute, therefore, by default the test execution is > disabled. Having a daily Jenkins job for the supported branches that execute > only this test suite would be nice. > The idea is the following: > * main - tests the latest SNAPSHOT > * 4.x branches, test the latest released 4.x camel jbang version (not the > SNAPSHOT), ex. camel-4.8.x will be tested via camel jbang 4.8.3 (latest 4.8.x > camel jbang release at this time) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21647) Create a jenkins job for Camel JBang IT test suite
[ https://issues.apache.org/jira/browse/CAMEL-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21647: - Fix Version/s: 4.10.0 (was: 4.x) > Create a jenkins job for Camel JBang IT test suite > -- > > Key: CAMEL-21647 > URL: https://issues.apache.org/jira/browse/CAMEL-21647 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Federico Mariani >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > > The [Camel JBang > IT|https://github.com/apache/camel/tree/main/dsl/camel-jbang/camel-jbang-it] > test suite is slow to execute, therefore, by default the test execution is > disabled. Having a daily Jenkins job for the supported branches that execute > only this test suite would be nice. > The idea is the following: > * main - tests the latest SNAPSHOT > * 4.x branches, test the latest released 4.x camel jbang version (not the > SNAPSHOT), ex. camel-4.8.x will be tested via camel jbang 4.8.3 (latest 4.8.x > camel jbang release at this time) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21598) Camel AWS Bedrock: Update supported models
[ https://issues.apache.org/jira/browse/CAMEL-21598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922424#comment-17922424 ] Andrea Cosentino commented on CAMEL-21598: -- Not yet. Moving to 4.11.0 > Camel AWS Bedrock: Update supported models > -- > > Key: CAMEL-21598 > URL: https://issues.apache.org/jira/browse/CAMEL-21598 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > > Some have been removed, some got new versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21678) Camel-Minio: Introducing Override Bucket Header in Producer operations
[ https://issues.apache.org/jira/browse/CAMEL-21678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21678. -- Resolution: Fixed > Camel-Minio: Introducing Override Bucket Header in Producer operations > -- > > Key: CAMEL-21678 > URL: https://issues.apache.org/jira/browse/CAMEL-21678 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > > Like CAMEL-20971 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21682) Camel-Google-Storage: Introducing Override Bucket Header in Producer operations
[ https://issues.apache.org/jira/browse/CAMEL-21682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21682. -- Resolution: Fixed > Camel-Google-Storage: Introducing Override Bucket Header in Producer > operations > --- > > Key: CAMEL-21682 > URL: https://issues.apache.org/jira/browse/CAMEL-21682 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21680) Camel-AWS2-S3: Introducing Override Bucket Header in Producer operations
[ https://issues.apache.org/jira/browse/CAMEL-21680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21680. -- Resolution: Fixed > Camel-AWS2-S3: Introducing Override Bucket Header in Producer operations > > > Key: CAMEL-21680 > URL: https://issues.apache.org/jira/browse/CAMEL-21680 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21678) Camel-Minio: Introducing Override Bucket Header in Producer operations
[ https://issues.apache.org/jira/browse/CAMEL-21678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21678: - Fix Version/s: 4.10.0 (was: 4.x) > Camel-Minio: Introducing Override Bucket Header in Producer operations > -- > > Key: CAMEL-21678 > URL: https://issues.apache.org/jira/browse/CAMEL-21678 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > > Like CAMEL-20971 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21678) Camel-Minio: Introducing Override Bucket Header in Producer operations
[ https://issues.apache.org/jira/browse/CAMEL-21678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21678: - Summary: Camel-Minio: Introducing Override Bucket Header in Producer operations (was: Camel-Minio: Define an header for the specific bucket name of the producer) > Camel-Minio: Introducing Override Bucket Header in Producer operations > -- > > Key: CAMEL-21678 > URL: https://issues.apache.org/jira/browse/CAMEL-21678 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > Like CAMEL-20971 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21682) Camel-Google-Storage: Introducing Override Bucket Header in Producer operations
Andrea Cosentino created CAMEL-21682: Summary: Camel-Google-Storage: Introducing Override Bucket Header in Producer operations Key: CAMEL-21682 URL: https://issues.apache.org/jira/browse/CAMEL-21682 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21680) Camel-AWS2-S3: Introducing Override Bucket Header in Producer operations
Andrea Cosentino created CAMEL-21680: Summary: Camel-AWS2-S3: Introducing Override Bucket Header in Producer operations Key: CAMEL-21680 URL: https://issues.apache.org/jira/browse/CAMEL-21680 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21678) Camel-Minio: Define an header for the specific bucket name of the producer
[ https://issues.apache.org/jira/browse/CAMEL-21678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21678: - Fix Version/s: 4.x (was: 4.10.0) > Camel-Minio: Define an header for the specific bucket name of the producer > -- > > Key: CAMEL-21678 > URL: https://issues.apache.org/jira/browse/CAMEL-21678 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > Like CAMEL-20971 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21678) Camel-Minio: Define an header for the specific bucket name of the producer
Andrea Cosentino created CAMEL-21678: Summary: Camel-Minio: Define an header for the specific bucket name of the producer Key: CAMEL-21678 URL: https://issues.apache.org/jira/browse/CAMEL-21678 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 Like CAMEL-20971 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (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:all-tabpanel ] Andrea Cosentino resolved CAMEL-21107. -- Resolution: Fixed > 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 > Components: camel-kubernetes >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21647) Create a jenkins job for Camel JBang IT test suite
[ https://issues.apache.org/jira/browse/CAMEL-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21647: Assignee: Andrea Cosentino > Create a jenkins job for Camel JBang IT test suite > -- > > Key: CAMEL-21647 > URL: https://issues.apache.org/jira/browse/CAMEL-21647 > Project: Camel > Issue Type: New Feature >Reporter: Federico Mariani >Assignee: Andrea Cosentino >Priority: Major > > The [Camel JBang > IT|https://github.com/apache/camel/tree/main/dsl/camel-jbang/camel-jbang-it] > test suite is slow to execute, therefore, by default the test execution is > disabled. Having a daily Jenkins job for the supported branches that execute > only this test suite would be nice. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21642) Camel-Hashicorp-Vault: Support Hashicorp cloud Vault instance in the pure component
[ https://issues.apache.org/jira/browse/CAMEL-21642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21642. -- Resolution: Fixed > Camel-Hashicorp-Vault: Support Hashicorp cloud Vault instance in the pure > component > > > Key: CAMEL-21642 > URL: https://issues.apache.org/jira/browse/CAMEL-21642 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21642) Camel-Hashicorp-Vault: Support Hashicorp cloud Vault instance in the pure component
Andrea Cosentino created CAMEL-21642: Summary: Camel-Hashicorp-Vault: Support Hashicorp cloud Vault instance in the pure component Key: CAMEL-21642 URL: https://issues.apache.org/jira/browse/CAMEL-21642 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21639) Camel-Hashicorp-Vault-Starter: Support Hashicorp Cloud deployment in properties function
[ https://issues.apache.org/jira/browse/CAMEL-21639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21639. -- Resolution: Fixed > Camel-Hashicorp-Vault-Starter: Support Hashicorp Cloud deployment in > properties function > > > Key: CAMEL-21639 > URL: https://issues.apache.org/jira/browse/CAMEL-21639 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21640) Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties function - Docs
[ https://issues.apache.org/jira/browse/CAMEL-21640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21640. -- Resolution: Fixed > Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties > function - Docs > --- > > Key: CAMEL-21640 > URL: https://issues.apache.org/jira/browse/CAMEL-21640 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21640) Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties function - Docs
Andrea Cosentino created CAMEL-21640: Summary: Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties function - Docs Key: CAMEL-21640 URL: https://issues.apache.org/jira/browse/CAMEL-21640 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21626) Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties function
[
https://issues.apache.org/jira/browse/CAMEL-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21626.
--
Resolution: Fixed
> Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties
> function
>
>
> Key: CAMEL-21626
> URL: https://issues.apache.org/jira/browse/CAMEL-21626
> Project: Camel
> Issue Type: New Feature
> Components: camel-hashicorp-vault
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.10.0
>
>
> Our current component is for on-prem hashicorp. If you use their cloud
> solution then you cannot use what we have today in Camel.
> I dont know if the cloud can use the java library or something else may be
> needed.
> But it would be good to have a security vault integration with this so you
> can use
> {code:java}
> {{hashicorp-cloud:myKey}} {code}
> placeholders in Camel routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21639) Camel-Hashicorp-Vault-Starter: Support Hashicorp Cloud deployment in properties function
Andrea Cosentino created CAMEL-21639: Summary: Camel-Hashicorp-Vault-Starter: Support Hashicorp Cloud deployment in properties function Key: CAMEL-21639 URL: https://issues.apache.org/jira/browse/CAMEL-21639 Project: Camel Issue Type: Task Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21626) Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties function
[
https://issues.apache.org/jira/browse/CAMEL-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21626:
-
Fix Version/s: 4.10.0
(was: 4.x)
> Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties
> function
>
>
> Key: CAMEL-21626
> URL: https://issues.apache.org/jira/browse/CAMEL-21626
> Project: Camel
> Issue Type: New Feature
> Components: camel-hashicorp-vault
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.10.0
>
>
> Our current component is for on-prem hashicorp. If you use their cloud
> solution then you cannot use what we have today in Camel.
> I dont know if the cloud can use the java library or something else may be
> needed.
> But it would be good to have a security vault integration with this so you
> can use
> {code:java}
> {{hashicorp-cloud:myKey}} {code}
> placeholders in Camel routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21626) Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties function
[
https://issues.apache.org/jira/browse/CAMEL-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21626:
-
Summary: Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in
properties function (was: hashicorp vault cloud component)
> Camel-Hashicorp-Vault: Support Hashicorp Cloud deployment in properties
> function
>
>
> Key: CAMEL-21626
> URL: https://issues.apache.org/jira/browse/CAMEL-21626
> Project: Camel
> Issue Type: New Feature
> Components: camel-hashicorp-vault
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.x
>
>
> Our current component is for on-prem hashicorp. If you use their cloud
> solution then you cannot use what we have today in Camel.
> I dont know if the cloud can use the java library or something else may be
> needed.
> But it would be good to have a security vault integration with this so you
> can use
> {code:java}
> {{hashicorp-cloud:myKey}} {code}
> placeholders in Camel routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21626) hashicorp vault cloud component
[
https://issues.apache.org/jira/browse/CAMEL-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914916#comment-17914916
]
Andrea Cosentino commented on CAMEL-21626:
--
This could be done directly in the same function. The only difference is the
presence of a namespace in the path. I'm working on it.
> hashicorp vault cloud component
> ---
>
> Key: CAMEL-21626
> URL: https://issues.apache.org/jira/browse/CAMEL-21626
> Project: Camel
> Issue Type: New Feature
> Components: camel-hashicorp-vault
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.x
>
>
> Our current component is for on-prem hashicorp. If you use their cloud
> solution then you cannot use what we have today in Camel.
> I dont know if the cloud can use the java library or something else may be
> needed.
> But it would be good to have a security vault integration with this so you
> can use
> {code:java}
> {{hashicorp-cloud:myKey}} {code}
> placeholders in Camel routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21626) hashicorp vault cloud component
[
https://issues.apache.org/jira/browse/CAMEL-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-21626:
Assignee: Andrea Cosentino
> hashicorp vault cloud component
> ---
>
> Key: CAMEL-21626
> URL: https://issues.apache.org/jira/browse/CAMEL-21626
> Project: Camel
> Issue Type: New Feature
> Components: camel-hashicorp-vault
>Reporter: Claus Ibsen
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.x
>
>
> Our current component is for on-prem hashicorp. If you use their cloud
> solution then you cannot use what we have today in Camel.
> I dont know if the cloud can use the java library or something else may be
> needed.
> But it would be good to have a security vault integration with this so you
> can use
> {code:java}
> {{hashicorp-cloud:myKey}} {code}
> placeholders in Camel routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21631) Enable Checksum algorithm on S3 streaming upload producer
[ https://issues.apache.org/jira/browse/CAMEL-21631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21631. -- Fix Version/s: 4.10.0 Resolution: Fixed > Enable Checksum algorithm on S3 streaming upload producer > - > > Key: CAMEL-21631 > URL: https://issues.apache.org/jira/browse/CAMEL-21631 > Project: Camel > Issue Type: Task > Components: camel-aws2-s3 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > > https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md#features-8 > and tests are failing https://github.com/apache/camel/actions/runs/12824983217 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21631) Enable Checksum algorithm on S3 streaming upload producer
Andrea Cosentino created CAMEL-21631: Summary: Enable Checksum algorithm on S3 streaming upload producer Key: CAMEL-21631 URL: https://issues.apache.org/jira/browse/CAMEL-21631 Project: Camel Issue Type: Task Components: camel-aws2-s3 Reporter: Andrea Cosentino Assignee: Andrea Cosentino https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md#features-8 and tests are failing https://github.com/apache/camel/actions/runs/12824983217 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21621) camel-jbang - k8s-httpclient-vertx fails in shutdown hook
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21621:
-
Fix Version/s: 4.10.0
> camel-jbang - k8s-httpclient-vertx fails in shutdown hook
> -
>
> Key: CAMEL-21621
> URL: https://issues.apache.org/jira/browse/CAMEL-21621
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.10.0
>
>
> {code}
> Exception in thread "Camel Thread #7 - CamelShutdownInterceptor"
> java.lang.RuntimeException: java.lang.IllegalStateException: Client is closed
> at
> org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesRun.lambda$installShutdownHook$10(KubernetesRun.java:514)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.IllegalStateException: Client is closed
> at
> io.vertx.core.http.impl.HttpClientImpl.checkClosed(HttpClientImpl.java:405)
> at
> io.vertx.core.http.impl.HttpClientImpl.doRequest(HttpClientImpl.java:281)
> at
> io.vertx.core.http.impl.HttpClientImpl.request(HttpClientImpl.java:191)
> at
> io.fabric8.kubernetes.client.vertx.VertxHttpRequest.consumeBytes(VertxHttpRequest.java:124)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21621) camel-jbang - k8s-httpclient-vertx fails in shutdown hook
[
https://issues.apache.org/jira/browse/CAMEL-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21621.
--
Resolution: Fixed
> camel-jbang - k8s-httpclient-vertx fails in shutdown hook
> -
>
> Key: CAMEL-21621
> URL: https://issues.apache.org/jira/browse/CAMEL-21621
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.10.0
>
>
> {code}
> Exception in thread "Camel Thread #7 - CamelShutdownInterceptor"
> java.lang.RuntimeException: java.lang.IllegalStateException: Client is closed
> at
> org.apache.camel.dsl.jbang.core.commands.kubernetes.KubernetesRun.lambda$installShutdownHook$10(KubernetesRun.java:514)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.IllegalStateException: Client is closed
> at
> io.vertx.core.http.impl.HttpClientImpl.checkClosed(HttpClientImpl.java:405)
> at
> io.vertx.core.http.impl.HttpClientImpl.doRequest(HttpClientImpl.java:281)
> at
> io.vertx.core.http.impl.HttpClientImpl.request(HttpClientImpl.java:191)
> at
> io.fabric8.kubernetes.client.vertx.VertxHttpRequest.consumeBytes(VertxHttpRequest.java:124)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21609) Blocked Threads After Upgrade
[ https://issues.apache.org/jira/browse/CAMEL-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912124#comment-17912124 ] Andrea Cosentino commented on CAMEL-21609: -- Without details about what your application is doing this issue is mostly useless > Blocked Threads After Upgrade > - > > Key: CAMEL-21609 > URL: https://issues.apache.org/jira/browse/CAMEL-21609 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-salesforce >Affects Versions: 4.4.4, 4.8.2, 4.9.0 >Reporter: Jawad Ahmad >Priority: Major > Attachments: image-2025-01-10-22-13-38-588.png, > image-2025-01-10-22-14-21-559.png > > > I recently upgraded my Camel application from Camel 3.2.1 and Java 11 to > Camel 4.9.0 and JDK 21. > I am now seeing a lot of blocked threads in thread monitoring. I noticed it > when my application started handing up during testing. I test on 4.4.4, > 4.8.2, and Java 11 as well. But seeing the same blocking there, > I also profiled my older Java 11 and Camel 3.2.1 instances, and there is no > blockage whatsoever. It works fine without any thread blocking. > !image-2025-01-10-22-14-21-559.png! > !image-2025-01-10-22-13-38-588.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21609) Blocked Threads After Upgrade
[ https://issues.apache.org/jira/browse/CAMEL-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21609: - Priority: Major (was: Critical) > Blocked Threads After Upgrade > - > > Key: CAMEL-21609 > URL: https://issues.apache.org/jira/browse/CAMEL-21609 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-salesforce >Affects Versions: 4.4.4, 4.8.2, 4.9.0 >Reporter: Jawad Ahmad >Priority: Major > Attachments: image-2025-01-10-22-13-38-588.png, > image-2025-01-10-22-14-21-559.png > > > I recently upgraded my Camel application from Camel 3.2.1 and Java 11 to > Camel 4.9.0 and JDK 21. > I am now seeing a lot of blocked threads in thread monitoring. I noticed it > when my application started handing up during testing. I test on 4.4.4, > 4.8.2, and Java 11 as well. But seeing the same blocking there, > I also profiled my older Java 11 and Camel 3.2.1 instances, and there is no > blockage whatsoever. It works fine without any thread blocking. > !image-2025-01-10-22-14-21-559.png! > !image-2025-01-10-22-13-38-588.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21598) Camel AWS Bedrock: Update supported models
[ https://issues.apache.org/jira/browse/CAMEL-21598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21598: - Fix Version/s: 4.10.0 (was: 4.11.0) > Camel AWS Bedrock: Update supported models > -- > > Key: CAMEL-21598 > URL: https://issues.apache.org/jira/browse/CAMEL-21598 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > > Some have been removed, some got new versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21598) Camel AWS Bedrock: Update supported models
[ https://issues.apache.org/jira/browse/CAMEL-21598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21598: - Fix Version/s: 4.11.0 (was: 4.10.0) > Camel AWS Bedrock: Update supported models > -- > > Key: CAMEL-21598 > URL: https://issues.apache.org/jira/browse/CAMEL-21598 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.11.0 > > > Some have been removed, some got new versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21597) Camel AWS Bedrock: Support Amazon Nova models
[ https://issues.apache.org/jira/browse/CAMEL-21597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21597: - Fix Version/s: 4.11.0 (was: 4.10.0) > Camel AWS Bedrock: Support Amazon Nova models > - > > Key: CAMEL-21597 > URL: https://issues.apache.org/jira/browse/CAMEL-21597 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.11.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21598) Camel AWS Bedrock: Update supported models
Andrea Cosentino created CAMEL-21598: Summary: Camel AWS Bedrock: Update supported models Key: CAMEL-21598 URL: https://issues.apache.org/jira/browse/CAMEL-21598 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 Some have been removed, some got new versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21597) Camel AWS Bedrock: Support Amazon Nova models
Andrea Cosentino created CAMEL-21597: Summary: Camel AWS Bedrock: Support Amazon Nova models Key: CAMEL-21597 URL: https://issues.apache.org/jira/browse/CAMEL-21597 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21593) camel-aws-ses - Add support for sending already created RawMessage
[ https://issues.apache.org/jira/browse/CAMEL-21593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21593: Assignee: Andrea Cosentino > camel-aws-ses - Add support for sending already created RawMessage > -- > > Key: CAMEL-21593 > URL: https://issues.apache.org/jira/browse/CAMEL-21593 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.x > > > [https://stackoverflow.com/questions/79329226/is-it-possible-to-send-a-rawmessage-using-apache-camel-aws-ses] > > The ses producer should check if the message body is already a ` > SendRawEmailRequest` and send it as-is -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21562) If HeadBucket call is not allowed, AWS2S3Endpoint fails to start
[ https://issues.apache.org/jira/browse/CAMEL-21562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21562. -- Resolution: Fixed > If HeadBucket call is not allowed, AWS2S3Endpoint fails to start > - > > Key: CAMEL-21562 > URL: https://issues.apache.org/jira/browse/CAMEL-21562 > Project: Camel > Issue Type: Bug > Components: camel-aws2-s3 >Affects Versions: 4.9.0 >Reporter: Michiel Meeuwissen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > > If for some reason it is not allowed to do the HeadBucket request in doStart > of > org.apache.camel.component.aws2.s3.AWS2S3Endpoint > > the entire route fails. This is unreasonable if > ! (isAutoCreateBucket) because nothing would happend any way. > > https://github.com/apache/camel/pull/16625 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21562) If HeadBucket call is not allowed, AWS2S3Endpoint fails to start
[ https://issues.apache.org/jira/browse/CAMEL-21562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21562: Assignee: Andrea Cosentino > If HeadBucket call is not allowed, AWS2S3Endpoint fails to start > - > > Key: CAMEL-21562 > URL: https://issues.apache.org/jira/browse/CAMEL-21562 > Project: Camel > Issue Type: Bug > Components: camel-aws2-s3 >Affects Versions: 4.9.0 >Reporter: Michiel Meeuwissen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > > If for some reason it is not allowed to do the HeadBucket request in doStart > of > org.apache.camel.component.aws2.s3.AWS2S3Endpoint > > the entire route fails. This is unreasonable if > ! (isAutoCreateBucket) because nothing would happend any way. > > https://github.com/apache/camel/pull/16625 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21562) If HeadBucket call is not allowed, AWS2S3Endpoint fails to start
[ https://issues.apache.org/jira/browse/CAMEL-21562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21562: - Fix Version/s: 4.8.3 4.10.0 > If HeadBucket call is not allowed, AWS2S3Endpoint fails to start > - > > Key: CAMEL-21562 > URL: https://issues.apache.org/jira/browse/CAMEL-21562 > Project: Camel > Issue Type: Bug > Components: camel-aws2-s3 >Affects Versions: 4.9.0 >Reporter: Michiel Meeuwissen >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > > If for some reason it is not allowed to do the HeadBucket request in doStart > of > org.apache.camel.component.aws2.s3.AWS2S3Endpoint > > the entire route fails. This is unreasonable if > ! (isAutoCreateBucket) because nothing would happend any way. > > https://github.com/apache/camel/pull/16625 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21562) If HeadBucket call is not allowed, AWS2S3Endpoint fails to start
[ https://issues.apache.org/jira/browse/CAMEL-21562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21562: - Priority: Minor (was: Major) > If HeadBucket call is not allowed, AWS2S3Endpoint fails to start > - > > Key: CAMEL-21562 > URL: https://issues.apache.org/jira/browse/CAMEL-21562 > Project: Camel > Issue Type: Bug > Components: camel-aws2-s3 >Affects Versions: 4.9.0 >Reporter: Michiel Meeuwissen >Priority: Minor > > If for some reason it is not allowed to do the HeadBucket request in doStart > of > org.apache.camel.component.aws2.s3.AWS2S3Endpoint > > the entire route fails. This is unreasonable if > ! (isAutoCreateBucket) because nothing would happend any way. > > https://github.com/apache/camel/pull/16625 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21553) Vault Properties Functions: Make it possible to use them even in bean instantiation
Andrea Cosentino created CAMEL-21553:
Summary: Vault Properties Functions: Make it possible to use them
even in bean instantiation
Key: CAMEL-21553
URL: https://issues.apache.org/jira/browse/CAMEL-21553
Project: Camel
Issue Type: New Feature
Reporter: Andrea Cosentino
Fix For: 4.x
Here is an reproducer through camel-jbang:
https://github.com/apache/camel-karavan/issues/1348#issuecomment-2545828481 in
Karavan
If you run this with camel-jbang and run a local hashicorp vault instance with
{code:java}
docker run --cap-add=IPC_LOCK -e 'VAULT_DEV_ROOT_TOKEN_ID=myroot'
hashicorp/vault
{code}
You'll notice that the secret won't be resolved. The problem could be in the
order we are configuring the vault and load the routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21526) camel-aws - Unable to set Timestamp in query parameters to initialize iterator of AT_TIMESTAMP type for AWS Kinesis component
[ https://issues.apache.org/jira/browse/CAMEL-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21526. -- Resolution: Fixed > camel-aws - Unable to set Timestamp in query parameters to initialize > iterator of AT_TIMESTAMP type for AWS Kinesis component > - > > Key: CAMEL-21526 > URL: https://issues.apache.org/jira/browse/CAMEL-21526 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.20.9, 4.9.0 >Reporter: Artem >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > Attachments: kinesis-timestamp-bug.zip > > > *Problem* > In AWS Kinesis, the iteratorType=AT_TIMESTAMP is an option that allows you to > start consuming records from a stream starting at a specific point in time. > To use iteratorType=AT_TIMESTAMP, we need to request the GetShardIterator > from AWS Kinesis API and specify Timestamp parameter for that request. > This message timestamp parameter must be set initially when we create AWS > Kinesis Consumer. > But in current Camel implementation unfortunately we don't have such ability. > You can see in docs > (https://camel.apache.org/components/next/aws2-kinesis-component.html) that > all we can is to set CamelMessageTimestamp message header. This way is not > suitable for initial setup of the iterator. > Apparently, the most suitable way is to set the timestamp in the URL options > (like for sequenceNumber). > *Steps to reproduce* > You can use the example project attached to this bug. > *Solution* > Possible solution you can find here: > https://github.com/apache/camel/commit/8772c5f2d4a57633447d2717dff53d87555b0e3b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21526) camel-aws - Unable to set Timestamp in query parameters to initialize iterator of AT_TIMESTAMP type for AWS Kinesis component
[ https://issues.apache.org/jira/browse/CAMEL-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21526: - Fix Version/s: 4.8.3 > camel-aws - Unable to set Timestamp in query parameters to initialize > iterator of AT_TIMESTAMP type for AWS Kinesis component > - > > Key: CAMEL-21526 > URL: https://issues.apache.org/jira/browse/CAMEL-21526 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.20.9, 4.9.0 >Reporter: Artem >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > Attachments: kinesis-timestamp-bug.zip > > > *Problem* > In AWS Kinesis, the iteratorType=AT_TIMESTAMP is an option that allows you to > start consuming records from a stream starting at a specific point in time. > To use iteratorType=AT_TIMESTAMP, we need to request the GetShardIterator > from AWS Kinesis API and specify Timestamp parameter for that request. > This message timestamp parameter must be set initially when we create AWS > Kinesis Consumer. > But in current Camel implementation unfortunately we don't have such ability. > You can see in docs > (https://camel.apache.org/components/next/aws2-kinesis-component.html) that > all we can is to set CamelMessageTimestamp message header. This way is not > suitable for initial setup of the iterator. > Apparently, the most suitable way is to set the timestamp in the URL options > (like for sequenceNumber). > *Steps to reproduce* > You can use the example project attached to this bug. > *Solution* > Possible solution you can find here: > https://github.com/apache/camel/commit/8772c5f2d4a57633447d2717dff53d87555b0e3b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21526) camel-aws - Unable to set Timestamp in query parameters to initialize iterator of AT_TIMESTAMP type for AWS Kinesis component
[ https://issues.apache.org/jira/browse/CAMEL-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21526: - Fix Version/s: 4.10.0 (was: 4.x) > camel-aws - Unable to set Timestamp in query parameters to initialize > iterator of AT_TIMESTAMP type for AWS Kinesis component > - > > Key: CAMEL-21526 > URL: https://issues.apache.org/jira/browse/CAMEL-21526 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.20.9, 4.9.0 >Reporter: Artem >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.10.0 > > Attachments: kinesis-timestamp-bug.zip > > > *Problem* > In AWS Kinesis, the iteratorType=AT_TIMESTAMP is an option that allows you to > start consuming records from a stream starting at a specific point in time. > To use iteratorType=AT_TIMESTAMP, we need to request the GetShardIterator > from AWS Kinesis API and specify Timestamp parameter for that request. > This message timestamp parameter must be set initially when we create AWS > Kinesis Consumer. > But in current Camel implementation unfortunately we don't have such ability. > You can see in docs > (https://camel.apache.org/components/next/aws2-kinesis-component.html) that > all we can is to set CamelMessageTimestamp message header. This way is not > suitable for initial setup of the iterator. > Apparently, the most suitable way is to set the timestamp in the URL options > (like for sequenceNumber). > *Steps to reproduce* > You can use the example project attached to this bug. > *Solution* > Possible solution you can find here: > https://github.com/apache/camel/commit/8772c5f2d4a57633447d2717dff53d87555b0e3b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21526) camel-aws - Unable to set Timestamp in query parameters to initialize iterator of AT_TIMESTAMP type for AWS Kinesis component
[ https://issues.apache.org/jira/browse/CAMEL-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21526: Assignee: Andrea Cosentino > camel-aws - Unable to set Timestamp in query parameters to initialize > iterator of AT_TIMESTAMP type for AWS Kinesis component > - > > Key: CAMEL-21526 > URL: https://issues.apache.org/jira/browse/CAMEL-21526 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.20.9, 4.9.0 >Reporter: Artem >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.x > > Attachments: kinesis-timestamp-bug.zip > > > *Problem* > In AWS Kinesis, the iteratorType=AT_TIMESTAMP is an option that allows you to > start consuming records from a stream starting at a specific point in time. > To use iteratorType=AT_TIMESTAMP, we need to request the GetShardIterator > from AWS Kinesis API and specify Timestamp parameter for that request. > This message timestamp parameter must be set initially when we create AWS > Kinesis Consumer. > But in current Camel implementation unfortunately we don't have such ability. > You can see in docs > (https://camel.apache.org/components/next/aws2-kinesis-component.html) that > all we can is to set CamelMessageTimestamp message header. This way is not > suitable for initial setup of the iterator. > Apparently, the most suitable way is to set the timestamp in the URL options > (like for sequenceNumber). > *Steps to reproduce* > You can use the example project attached to this bug. > *Solution* > Possible solution you can find here: > https://github.com/apache/camel/commit/8772c5f2d4a57633447d2717dff53d87555b0e3b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21496) Camel-Azure-Key-Vault: Add Update Secret operation to Producer
[ https://issues.apache.org/jira/browse/CAMEL-21496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21496. -- Resolution: Fixed > Camel-Azure-Key-Vault: Add Update Secret operation to Producer > -- > > Key: CAMEL-21496 > URL: https://issues.apache.org/jira/browse/CAMEL-21496 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21483) Camel-upgrade-recipes: cover upgrading camel 4.8 to 4.9
[ https://issues.apache.org/jira/browse/CAMEL-21483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902291#comment-17902291 ] Andrea Cosentino commented on CAMEL-21483: -- It's good from my pov. > Camel-upgrade-recipes: cover upgrading camel 4.8 to 4.9 > --- > > Key: CAMEL-21483 > URL: https://issues.apache.org/jira/browse/CAMEL-21483 > Project: Camel > Issue Type: Task > Components: upgrade-recipes >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Cover migrations described by [migration > guide|https://github.com/apache/camel/blob/main/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_9.adoc] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21497) Camel-Kubernetes: Add Configmap Dev Console
[ https://issues.apache.org/jira/browse/CAMEL-21497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21497. -- Resolution: Fixed > Camel-Kubernetes: Add Configmap Dev Console > --- > > Key: CAMEL-21497 > URL: https://issues.apache.org/jira/browse/CAMEL-21497 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21497) Camel-Kubernetes: Add Configmap Dev Console
Andrea Cosentino created CAMEL-21497: Summary: Camel-Kubernetes: Add Configmap Dev Console Key: CAMEL-21497 URL: https://issues.apache.org/jira/browse/CAMEL-21497 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21496) Camel-Azure-Key-Vault: Add Update Secret operation to Producer
Andrea Cosentino created CAMEL-21496: Summary: Camel-Azure-Key-Vault: Add Update Secret operation to Producer Key: CAMEL-21496 URL: https://issues.apache.org/jira/browse/CAMEL-21496 Project: Camel Issue Type: New Feature Components: camel-azure Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.10.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21486) camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000
Andrea Cosentino created CAMEL-21486: Summary: camel k8s ... cannot push to image-registry.openshift-image-registry.svc:5000 Key: CAMEL-21486 URL: https://issues.apache.org/jira/browse/CAMEL-21486 Project: Camel Issue Type: Bug Affects Versions: 4.8.1 Reporter: Andrea Cosentino Assignee: Thomas Diesler -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21477) Camel-Google-Storage: Add prefix option to consumer
[ https://issues.apache.org/jira/browse/CAMEL-21477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21477. -- Resolution: Fixed > Camel-Google-Storage: Add prefix option to consumer > --- > > Key: CAMEL-21477 > URL: https://issues.apache.org/jira/browse/CAMEL-21477 > Project: Camel > Issue Type: Improvement > Components: camel-google >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-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=17901649#comment-17901649 ] Andrea Cosentino commented on CAMEL-21107: -- Yes, there are still producers to work on. > 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] [Commented] (CAMEL-21385) Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration'
[ https://issues.apache.org/jira/browse/CAMEL-21385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901458#comment-17901458 ] Andrea Cosentino commented on CAMEL-21385: -- https://github.com/apache/camel-kamelets/issues/2278 This should resolve the problem, without any other addition > Camel-Jbang: Spring Boot export with SQL Kamelets requires > 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' > - > > Key: CAMEL-21385 > URL: https://issues.apache.org/jira/browse/CAMEL-21385 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > > This is something useful because otherwise the application will fail, because > spring datasource will do autoconfiguration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21477) Camel-Google-Storage: Add prefix option to consumer
Andrea Cosentino created CAMEL-21477: Summary: Camel-Google-Storage: Add prefix option to consumer Key: CAMEL-21477 URL: https://issues.apache.org/jira/browse/CAMEL-21477 Project: Camel Issue Type: Improvement Components: camel-google 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-21385) Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration'
[ https://issues.apache.org/jira/browse/CAMEL-21385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21385. -- Resolution: Won't Fix > Camel-Jbang: Spring Boot export with SQL Kamelets requires > 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' > - > > Key: CAMEL-21385 > URL: https://issues.apache.org/jira/browse/CAMEL-21385 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > > This is something useful because otherwise the application will fail, because > spring datasource will do autoconfiguration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21476) SQL Stored Procedure compont don't use definied RowMapperFactory from SQL compont
[
https://issues.apache.org/jira/browse/CAMEL-21476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901424#comment-17901424
]
Andrea Cosentino commented on CAMEL-21476:
--
The Spring Boot section is mixed between sql and sql-stored properties, because
the component contains two different components SQL and SQL stored, if you're
using SQL stored component, you should look only to sql-stored properties, so
RowMapperFactory is not supported.
> SQL Stored Procedure compont don't use definied RowMapperFactory from SQL
> compont
> --
>
> Key: CAMEL-21476
> URL: https://issues.apache.org/jira/browse/CAMEL-21476
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 4.8.0
>Reporter: John Zander
>Priority: Minor
> Fix For: 4.x
>
>
> {color:#268bd2}Hi devs,{color}
>
> {color:#268bd2}we are using camel to call stored-procedures which return a
> non-standard datatype which is not handled by the framework. For this use
> case, it is possible to define a custom RowMapperFactory which can handle
> that datatype. {color}
>
> {color:#268bd2}[https://camel.apache.org/components/4.8.x/sql-stored-component.html]{color}
>
> {color:#268bd2}states
> {color}{color:#268bd2}"camel.component.{color}{color:#268bd2}sql.{color}{color:#268bd2}row-mapper-factory"
> as property to set.{color}
>
> Unfortunately, this property doesn't become active on "sqlstored" only on
> plain "sql". Please fix or change the documentation with the correct
> property. Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21476) SQL Stored Procedure compont don't use definied RowMapperFactory from SQL compont
[
https://issues.apache.org/jira/browse/CAMEL-21476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21476.
--
Resolution: Information Provided
> SQL Stored Procedure compont don't use definied RowMapperFactory from SQL
> compont
> --
>
> Key: CAMEL-21476
> URL: https://issues.apache.org/jira/browse/CAMEL-21476
> Project: Camel
> Issue Type: Improvement
> Components: camel-sql
>Affects Versions: 4.8.0
>Reporter: John Zander
>Priority: Minor
> Fix For: 4.x
>
>
> {color:#268bd2}Hi devs,{color}
>
> {color:#268bd2}we are using camel to call stored-procedures which return a
> non-standard datatype which is not handled by the framework. For this use
> case, it is possible to define a custom RowMapperFactory which can handle
> that datatype. {color}
>
> {color:#268bd2}[https://camel.apache.org/components/4.8.x/sql-stored-component.html]{color}
>
> {color:#268bd2}states
> {color}{color:#268bd2}"camel.component.{color}{color:#268bd2}sql.{color}{color:#268bd2}row-mapper-factory"
> as property to set.{color}
>
> Unfortunately, this property doesn't become active on "sqlstored" only on
> plain "sql". Please fix or change the documentation with the correct
> property. Thank you!
--
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: - Fix Version/s: (was: 4.9.0) (was: 4.8.2) > 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 > Components: camel-google >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > > 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-21166) Kubernetes Configmaps: Trigger context reloading on update
[ https://issues.apache.org/jira/browse/CAMEL-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21166. -- Resolution: Fixed > Kubernetes Configmaps: Trigger context reloading on update > -- > > Key: CAMEL-21166 > URL: https://issues.apache.org/jira/browse/CAMEL-21166 > Project: Camel > Issue Type: New Feature > Components: camel-kubernetes >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-21453) Camel-Spring-Boot: Kubernetes Configmaps Trigger context reloading on update
[ https://issues.apache.org/jira/browse/CAMEL-21453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21453. -- Resolution: Fixed > Camel-Spring-Boot: Kubernetes Configmaps Trigger context reloading on update > > > Key: CAMEL-21453 > URL: https://issues.apache.org/jira/browse/CAMEL-21453 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > Related to CAMEL-21166 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21458) Kubernetes Configmaps: Trigger context reloading on update - Documentation
[ https://issues.apache.org/jira/browse/CAMEL-21458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21458. -- Resolution: Fixed > Kubernetes Configmaps: Trigger context reloading on update - Documentation > -- > > Key: CAMEL-21458 > URL: https://issues.apache.org/jira/browse/CAMEL-21458 > Project: Camel > Issue Type: Sub-task >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-21458) Kubernetes Configmaps: Trigger context reloading on update - Documentation
Andrea Cosentino created CAMEL-21458: Summary: Kubernetes Configmaps: Trigger context reloading on update - Documentation Key: CAMEL-21458 URL: https://issues.apache.org/jira/browse/CAMEL-21458 Project: Camel Issue Type: Sub-task 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-21453) Camel-Spring-Boot: Kubernetes Configmaps Trigger context reloading on update
Andrea Cosentino created CAMEL-21453: Summary: Camel-Spring-Boot: Kubernetes Configmaps Trigger context reloading on update Key: CAMEL-21453 URL: https://issues.apache.org/jira/browse/CAMEL-21453 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.9.0 Related to CAMEL-21166 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21446:
-
Fix Version/s: 4.8.2
4.9.0
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Assignee: Marco Carletti
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namespace: default
> masterUrl: kubernetes.default.svc:443
> operation: listConfigMaps
> - marshal:
> id: marshal-55e5
> json:
> id: json-b0d1
> - log:
> id: log-d04e
> message: >-
> Printing test configmap without default
> {{configmap:secondmap/test}}
> - log:
> id: log-3396
> message: Printing test secret without default
> {{secret:secondsecret/test}}
> - log:
> id: log-f123
> message: >-
> Printing test configmap with default
> {{configmap:secondmap/test:default}}
> - log:
> id: log-f123
> message: >-
> Printing test secret with default
> {{configmap:secondsecret/test:default}} {code}
> Output in my testing minikube container:
> {code:java}
> 2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
> : Printing test configmap without default working
> 2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
> : Printing test secret without default mysecretvalue
> 2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
> : Printing test configmap with default default
> 2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
> : Printing test secret with default default {code}
> So when using the default in property placeholders it will take precedence
> even if given key is present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21445) camel-core - Vault with secret refresh should be disabled as default
[ https://issues.apache.org/jira/browse/CAMEL-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21445. -- Resolution: Fixed > camel-core - Vault with secret refresh should be disabled as default > > > Key: CAMEL-21445 > URL: https://issues.apache.org/jira/browse/CAMEL-21445 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-main >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > See chat > [https://camel.zulipchat.com/#narrow/channel/352237-camel-jbang/topic/export.20with.20vault] > > Change the default to false in the camel-main vault configuration. > Add note about this change in the 4.9 upgrade guide > To enable you just set > camel.vault.kubernetes.refreshEnabled=true > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-21446:
Assignee: Marco Carletti
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Assignee: Marco Carletti
>Priority: Minor
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namespace: default
> masterUrl: kubernetes.default.svc:443
> operation: listConfigMaps
> - marshal:
> id: marshal-55e5
> json:
> id: json-b0d1
> - log:
> id: log-d04e
> message: >-
> Printing test configmap without default
> {{configmap:secondmap/test}}
> - log:
> id: log-3396
> message: Printing test secret without default
> {{secret:secondsecret/test}}
> - log:
> id: log-f123
> message: >-
> Printing test configmap with default
> {{configmap:secondmap/test:default}}
> - log:
> id: log-f123
> message: >-
> Printing test secret with default
> {{configmap:secondsecret/test:default}} {code}
> Output in my testing minikube container:
> {code:java}
> 2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
> : Printing test configmap without default working
> 2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
> : Printing test secret without default mysecretvalue
> 2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
> : Printing test configmap with default default
> 2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
> : Printing test secret with default default {code}
> So when using the default in property placeholders it will take precedence
> even if given key is present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21445) camel-core - Vault with secret refresh should be disabled as default
[ https://issues.apache.org/jira/browse/CAMEL-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21445: - Fix Version/s: 4.8.2 > camel-core - Vault with secret refresh should be disabled as default > > > Key: CAMEL-21445 > URL: https://issues.apache.org/jira/browse/CAMEL-21445 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-main >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > See chat > [https://camel.zulipchat.com/#narrow/channel/352237-camel-jbang/topic/export.20with.20vault] > > Change the default to false in the camel-main vault configuration. > Add note about this change in the 4.9 upgrade guide > To enable you just set > camel.vault.kubernetes.refreshEnabled=true > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21446) configmap/secret - default takes precedence
[
https://issues.apache.org/jira/browse/CAMEL-21446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897895#comment-17897895
]
Andrea Cosentino commented on CAMEL-21446:
--
[~mcarlett] already has a fix
> configmap/secret - default takes precedence
> ---
>
> Key: CAMEL-21446
> URL: https://issues.apache.org/jira/browse/CAMEL-21446
> Project: Camel
> Issue Type: Bug
> Components: camel-kubernetes
>Affects Versions: 4.8.1
>Reporter: Filip Jalaksa
>Assignee: Marco Carletti
>Priority: Minor
>
> Created a simple integration using Karavan
> {code:java}
> - rest:
> id: rest-d471
> post:
> - id: post-126a
> path: /injectionTest
> to: direct:injectionTest
> - route:
> id: route-a292
> from:
> id: from-b12a
> uri: direct
> parameters:
> name: injectionTest
> steps:
> - to:
> id: to-bab9
> uri: kubernetes-config-maps
> parameters:
> namespace: default
> masterUrl: kubernetes.default.svc:443
> operation: listConfigMaps
> - marshal:
> id: marshal-55e5
> json:
> id: json-b0d1
> - log:
> id: log-d04e
> message: >-
> Printing test configmap without default
> {{configmap:secondmap/test}}
> - log:
> id: log-3396
> message: Printing test secret without default
> {{secret:secondsecret/test}}
> - log:
> id: log-f123
> message: >-
> Printing test configmap with default
> {{configmap:secondmap/test:default}}
> - log:
> id: log-f123
> message: >-
> Printing test secret with default
> {{configmap:secondsecret/test:default}} {code}
> Output in my testing minikube container:
> {code:java}
> 2024-11-13 09:56:49.377 INFO 1 --- [worker-thread-0] configmap.camel.yaml:26
> : Printing test configmap without default working
> 2024-11-13 09:56:49.380 INFO 1 --- [worker-thread-0] configmap.camel.yaml:31
> : Printing test secret without default mysecretvalue
> 2024-11-13 09:56:49.382 INFO 1 --- [worker-thread-0] configmap.camel.yaml:34
> : Printing test configmap with default default
> 2024-11-13 09:56:49.383 INFO 1 --- [worker-thread-0] configmap.camel.yaml:39
> : Printing test secret with default default {code}
> So when using the default in property placeholders it will take precedence
> even if given key is present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21445) camel-core - Vault with secret refresh should be disabled as default
[ https://issues.apache.org/jira/browse/CAMEL-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21445: Assignee: Andrea Cosentino > camel-core - Vault with secret refresh should be disabled as default > > > Key: CAMEL-21445 > URL: https://issues.apache.org/jira/browse/CAMEL-21445 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-main >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.9.0 > > > See chat > [https://camel.zulipchat.com/#narrow/channel/352237-camel-jbang/topic/export.20with.20vault] > > Change the default to false in the camel-main vault configuration. > Add note about this change in the 4.9 upgrade guide > To enable you just set > camel.vault.kubernetes.refreshEnabled=true > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21421) Move assertj version to parent
[ https://issues.apache.org/jira/browse/CAMEL-21421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21421: Assignee: Andrea Cosentino > Move assertj version to parent > -- > > Key: CAMEL-21421 > URL: https://issues.apache.org/jira/browse/CAMEL-21421 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Adriano Machado >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-13488) camel-infinispan support counters
[ https://issues.apache.org/jira/browse/CAMEL-13488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13488. -- Resolution: Abandoned > camel-infinispan support counters > - > > Key: CAMEL-13488 > URL: https://issues.apache.org/jira/browse/CAMEL-13488 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Reporter: Luca Burgazzoli >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.x > > > We should support operations against infinispan counters, see > https://github.com/infinispan/infinispan/blob/master/documentation/src/main/asciidoc/user_guide/counters.adoc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-21421) Move assertj version to parent
[ https://issues.apache.org/jira/browse/CAMEL-21421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21421 started by Andrea Cosentino. > Move assertj version to parent > -- > > Key: CAMEL-21421 > URL: https://issues.apache.org/jira/browse/CAMEL-21421 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Adriano Machado >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (CAMEL-21421) Move assertj version to parent
[ https://issues.apache.org/jira/browse/CAMEL-21421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21421 stopped by Andrea Cosentino. > Move assertj version to parent > -- > > Key: CAMEL-21421 > URL: https://issues.apache.org/jira/browse/CAMEL-21421 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Adriano Machado >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21421) Move assertj version to parent
[ https://issues.apache.org/jira/browse/CAMEL-21421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21421. -- Resolution: Fixed > Move assertj version to parent > -- > > Key: CAMEL-21421 > URL: https://issues.apache.org/jira/browse/CAMEL-21421 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Adriano Machado >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21421) Move assertj version to parent
[ https://issues.apache.org/jira/browse/CAMEL-21421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21421: - Fix Version/s: 4.9.0 > Move assertj version to parent > -- > > Key: CAMEL-21421 > URL: https://issues.apache.org/jira/browse/CAMEL-21421 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Adriano Machado >Priority: Minor > Fix For: 4.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21385) Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' to be f
Andrea Cosentino created CAMEL-21385: Summary: Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' to be false Key: CAMEL-21385 URL: https://issues.apache.org/jira/browse/CAMEL-21385 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Andrea Cosentino Assignee: Andrea Cosentino This is something useful because otherwise the application will fail, because spring datasource will do autoconfiguration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21385) Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration'
[ https://issues.apache.org/jira/browse/CAMEL-21385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21385: - Summary: Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' (was: Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' to be false) > Camel-Jbang: Spring Boot export with SQL Kamelets requires > 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' > - > > Key: CAMEL-21385 > URL: https://issues.apache.org/jira/browse/CAMEL-21385 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > > This is something useful because otherwise the application will fail, because > spring datasource will do autoconfiguration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21375) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack in Spring Boot
[ https://issues.apache.org/jira/browse/CAMEL-21375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21375. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Support Properties Function with Localstack in > Spring Boot > - > > Key: CAMEL-21375 > URL: https://issues.apache.org/jira/browse/CAMEL-21375 > Project: Camel > Issue Type: Improvement > 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] [Resolved] (CAMEL-21330) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack
[ https://issues.apache.org/jira/browse/CAMEL-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21330. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Support Properties Function with Localstack > -- > > Key: CAMEL-21330 > URL: https://issues.apache.org/jira/browse/CAMEL-21330 > Project: Camel > Issue Type: New Feature >Reporter: Lukas Lowinger >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > > To make Localstack work we need to set correct *endpointOverride* which is > done in the [common aws > client|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/client/impl/SecretsManagerClientStandardImpl.java#L90] > used in Camel. The problem is > [PropertiesFunction|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/SecretsManagerPropertiesFunction.java#L138] > doesn't provide such option. > Just for reference, here is > [code|https://github.com/apache/camel-quarkus/blob/main/integration-tests-support/aws2/src/test/java/org/apache/camel/quarkus/test/support/aws2/Aws2TestEnvContext.java#L185] > which sets it in Camel Quarkus project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21375) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack in Spring Boot
Andrea Cosentino created CAMEL-21375: Summary: Camel-AWS-Secrets-Manager: Support Properties Function with Localstack in Spring Boot Key: CAMEL-21375 URL: https://issues.apache.org/jira/browse/CAMEL-21375 Project: Camel Issue Type: Improvement 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-21330) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack
[ https://issues.apache.org/jira/browse/CAMEL-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21330: - Fix Version/s: 4.9.0 (was: 4.x) > Camel-AWS-Secrets-Manager: Support Properties Function with Localstack > -- > > Key: CAMEL-21330 > URL: https://issues.apache.org/jira/browse/CAMEL-21330 > Project: Camel > Issue Type: New Feature >Reporter: Lukas Lowinger >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.9.0 > > > To make Localstack work we need to set correct *endpointOverride* which is > done in the [common aws > client|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/client/impl/SecretsManagerClientStandardImpl.java#L90] > used in Camel. The problem is > [PropertiesFunction|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/SecretsManagerPropertiesFunction.java#L138] > doesn't provide such option. > Just for reference, here is > [code|https://github.com/apache/camel-quarkus/blob/main/integration-tests-support/aws2/src/test/java/org/apache/camel/quarkus/test/support/aws2/Aws2TestEnvContext.java#L185] > which sets it in Camel Quarkus project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21373) Camel-AWS-Secrets-Manager: Delete operation add an header for forcing the deletion
[ https://issues.apache.org/jira/browse/CAMEL-21373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21373. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Delete operation add an header for forcing the > deletion > -- > > Key: CAMEL-21373 > URL: https://issues.apache.org/jira/browse/CAMEL-21373 > 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] [Created] (CAMEL-21373) Camel-AWS-Secrets-Manager: Delete operation add an header for forcing the deletion
Andrea Cosentino created CAMEL-21373: Summary: Camel-AWS-Secrets-Manager: Delete operation add an header for forcing the deletion Key: CAMEL-21373 URL: https://issues.apache.org/jira/browse/CAMEL-21373 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] [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:
-
Component/s: (was: camel-hashicorp-vault)
> 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-spring-boot
>Reporter: Federico Mariani
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.9.0
>
>
> 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-21360) Camel Spring Boot: Vault early resolving properties documentation
[ https://issues.apache.org/jira/browse/CAMEL-21360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21360. -- Resolution: Fixed > Camel Spring Boot: Vault early resolving properties documentation > - > > Key: CAMEL-21360 > URL: https://issues.apache.org/jira/browse/CAMEL-21360 > Project: Camel > Issue Type: Sub-task > 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] [Resolved] (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 resolved CAMEL-21265.
--
Resolution: Fixed
> 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.9.0
>
>
> 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] [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.9.0
(was: 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.9.0
>
>
> 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-21360) Camel Spring Boot: Vault early resolving properties documentation
Andrea Cosentino created CAMEL-21360: Summary: Camel Spring Boot: Vault early resolving properties documentation Key: CAMEL-21360 URL: https://issues.apache.org/jira/browse/CAMEL-21360 Project: Camel Issue Type: Sub-task 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] [Comment Edited] (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 edited comment on CAMEL-21265 at 10/17/24 11:03 AM:
-
Thanks [~Federico Mariani] for the Hashicorp part.
I'm going to do the same for AWS, GCP and Azure
Hashicorp - done
AWS - done
GCP - done
Azure Key Vault - Done
was (Author: ancosen):
Thanks [~Federico Mariani] for the Hashicorp part.
I'm going to do the same for AWS, GCP and Azure
Hashicorp - done
AWS - done
GCP - done
> 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] [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=17890170#comment-17890170
]
Andrea Cosentino commented on CAMEL-21265:
--
We need to add a section about early resolving properties in the Spring Boot
section of the components doc.
> 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] [Comment Edited] (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 edited comment on CAMEL-21265 at 10/16/24 4:26 PM:
Thanks [~Federico Mariani] for the Hashicorp part.
I'm going to do the same for AWS, GCP and Azure
Hashicorp - done
AWS - done
GCP - done
was (Author: ancosen):
Thanks [~Federico Mariani] for the Hashicorp part.
I'm going to do the same for AWS, GCP and Azure
Hashicorp - done
AWS - done
> 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] [Commented] (CAMEL-21314) camel-aws - Fix S3CopyObjectCustomerKeyIT.sendIn which is failing on main branch
[
https://issues.apache.org/jira/browse/CAMEL-21314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889505#comment-17889505
]
Andrea Cosentino commented on CAMEL-21314:
--
I'll have a look this week.
> camel-aws - Fix S3CopyObjectCustomerKeyIT.sendIn which is failing on main
> branch
>
>
> Key: CAMEL-21314
> URL: https://issues.apache.org/jira/browse/CAMEL-21314
> Project: Camel
> Issue Type: Task
> Components: camel-aws2
>Affects Versions: 4.8.0
>Reporter: Aurélien Pupier
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.x
>
>
> it is currently not possible. There is this test in error:
> {noformat}
> [[1;31mERROR[m] [1;31mTests [0;1mrun: [0;1m1[m, [1;31mFailures:
> [0;1;31m1[m, Errors: 0, Skipped: 0, Time elapsed: 0.160 s[1;31m <<<
> FAILURE![m -- in
> org.apache.camel.component.aws2.s3.integration.[1mS3CopyObjectCustomerKeyIT[m
> [[1;31mERROR[m]
> org.apache.camel.component.aws2.s3.integration.S3CopyObjectCustomerKeyIT.sendIn
> -- Time elapsed: 0.153 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: not
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:152)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at org.junit.jupiter.api.AssertNotNull.failNull(AssertNotNull.java:49)
> at
> org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:35)
> at
> org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:30)
> at org.junit.jupiter.api.Assertions.assertNotNull(Assertions.java:304)
> at
> org.apache.camel.component.aws2.s3.integration.S3CopyObjectCustomerKeyIT.sendIn(S3CopyObjectCustomerKeyIT.java:98)
> at java.base/java.lang.reflect.Method.invoke(Method.java:569)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> {noformat}
> Tried with localstack/localstack:3.7.0 and localstack/localstack:3.7.2
> to investigate if it is just a matter of test update or there is a real
> breakage with latest version of AWS
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21314) camel-aws - Fix S3CopyObjectCustomerKeyIT.sendIn which is failing on main branch
[
https://issues.apache.org/jira/browse/CAMEL-21314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-21314:
Assignee: Andrea Cosentino
> camel-aws - Fix S3CopyObjectCustomerKeyIT.sendIn which is failing on main
> branch
>
>
> Key: CAMEL-21314
> URL: https://issues.apache.org/jira/browse/CAMEL-21314
> Project: Camel
> Issue Type: Task
> Components: camel-aws2
>Affects Versions: 4.8.0
>Reporter: Aurélien Pupier
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.x
>
>
> it is currently not possible. There is this test in error:
> {noformat}
> [[1;31mERROR[m] [1;31mTests [0;1mrun: [0;1m1[m, [1;31mFailures:
> [0;1;31m1[m, Errors: 0, Skipped: 0, Time elapsed: 0.160 s[1;31m <<<
> FAILURE![m -- in
> org.apache.camel.component.aws2.s3.integration.[1mS3CopyObjectCustomerKeyIT[m
> [[1;31mERROR[m]
> org.apache.camel.component.aws2.s3.integration.S3CopyObjectCustomerKeyIT.sendIn
> -- Time elapsed: 0.153 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: not
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:152)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at org.junit.jupiter.api.AssertNotNull.failNull(AssertNotNull.java:49)
> at
> org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:35)
> at
> org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:30)
> at org.junit.jupiter.api.Assertions.assertNotNull(Assertions.java:304)
> at
> org.apache.camel.component.aws2.s3.integration.S3CopyObjectCustomerKeyIT.sendIn(S3CopyObjectCustomerKeyIT.java:98)
> at java.base/java.lang.reflect.Method.invoke(Method.java:569)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> {noformat}
> Tried with localstack/localstack:3.7.0 and localstack/localstack:3.7.2
> to investigate if it is just a matter of test update or there is a real
> breakage with latest version of AWS
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21330) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack
[ https://issues.apache.org/jira/browse/CAMEL-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21330: Assignee: Andrea Cosentino > Camel-AWS-Secrets-Manager: Support Properties Function with Localstack > -- > > Key: CAMEL-21330 > URL: https://issues.apache.org/jira/browse/CAMEL-21330 > Project: Camel > Issue Type: New Feature >Reporter: Lukas Lowinger >Assignee: Andrea Cosentino >Priority: Minor > > To make Localstack work we need to set correct *endpointOverride* which is > done in the [common aws > client|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/client/impl/SecretsManagerClientStandardImpl.java#L90] > used in Camel. The problem is > [PropertiesFunction|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/SecretsManagerPropertiesFunction.java#L138] > doesn't provide such option. > Just for reference, here is > [code|https://github.com/apache/camel-quarkus/blob/main/integration-tests-support/aws2/src/test/java/org/apache/camel/quarkus/test/support/aws2/Aws2TestEnvContext.java#L185] > which sets it in Camel Quarkus project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21330) Camel-AWS-Secrets-Manager: Support Properties Function with Localstack
[ https://issues.apache.org/jira/browse/CAMEL-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21330: - Fix Version/s: 4.x > Camel-AWS-Secrets-Manager: Support Properties Function with Localstack > -- > > Key: CAMEL-21330 > URL: https://issues.apache.org/jira/browse/CAMEL-21330 > Project: Camel > Issue Type: New Feature >Reporter: Lukas Lowinger >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.x > > > To make Localstack work we need to set correct *endpointOverride* which is > done in the [common aws > client|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/client/impl/SecretsManagerClientStandardImpl.java#L90] > used in Camel. The problem is > [PropertiesFunction|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws-secrets-manager/src/main/java/org/apache/camel/component/aws/secretsmanager/SecretsManagerPropertiesFunction.java#L138] > doesn't provide such option. > Just for reference, here is > [code|https://github.com/apache/camel-quarkus/blob/main/integration-tests-support/aws2/src/test/java/org/apache/camel/quarkus/test/support/aws2/Aws2TestEnvContext.java#L185] > which sets it in Camel Quarkus project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (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 edited comment on CAMEL-21265 at 10/14/24 1:48 PM:
Thanks [~Federico Mariani] for the Hashicorp part.
I'm going to do the same for AWS, GCP and Azure
Hashicorp - done
AWS - done
was (Author: ancosen):
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] [Commented] (CAMEL-21334) Camel-opensearch - Provide ppc64le arch support
[ https://issues.apache.org/jira/browse/CAMEL-21334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889201#comment-17889201 ] Andrea Cosentino commented on CAMEL-21334: -- For the time being I would simply revert this stuff. > 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] [Commented] (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:comment-tabpanel&focusedCommentId=17888635#comment-17888635 ] Andrea Cosentino commented on CAMEL-21249: -- Removed also the stuff on Kamelets side and all seems to work. > 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)
