[jira] [Assigned] (CAMEL-20775) camel-hashicorp-vault - configure multiple engines
[
https://issues.apache.org/jira/browse/CAMEL-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-20775:
Assignee: Andrea Cosentino
> camel-hashicorp-vault - configure multiple engines
> --
>
> Key: CAMEL-20775
> URL: https://issues.apache.org/jira/browse/CAMEL-20775
> Project: Camel
> Issue Type: Improvement
> Components: camel-hashicorp-vault
>Reporter: Federico Mariani
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.x
>
>
> Currently, only one engine can be (easily) configured in the
> camel-hashicorp-vault component.
> It would be nice to configure the engine ala
> \{{hashicorp:engine:path/to/secret}} so that multiple engines can be used in
> the same application. for example, key/value store engine and pki store
> engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847683#comment-17847683 ] Jang-Vijay Singh commented on CAMEL-20722: -- Some proposed changes added to address the specific flaky tests: [https://github.com/apache/camel/pull/14183] > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.x > > Attachments: build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19964) camel-rest- Consumer support request param
[ https://issues.apache.org/jira/browse/CAMEL-19964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19964. - Resolution: Won't Fix > camel-rest- Consumer support request param > -- > > Key: CAMEL-19964 > URL: https://issues.apache.org/jira/browse/CAMEL-19964 > Project: Camel > Issue Type: New Feature > Components: rest >Reporter: tanyu >Priority: Minor > > when camel-rest as consumer can support uri template,similar to the > PathVariable Annotation in spring. So, Can we support request param in camel > just like RequestParam in Spring? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19869) spring-boot - Fix some ISPN integration tests
[
https://issues.apache.org/jira/browse/CAMEL-19869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19869:
Priority: Minor (was: Major)
> spring-boot - Fix some ISPN integration tests
> --
>
> Key: CAMEL-19869
> URL: https://issues.apache.org/jira/browse/CAMEL-19869
> Project: Camel
> Issue Type: Task
> Components: camel-infinispan
>Affects Versions: 4.0.0
>Reporter: Nicolas Filotto
>Priority: Minor
>
> The integration tests {{InfinispanRemoteAggregationRepositoryIT}} and
> {{InfinispanRemoteAggregationRepositoryOperationsIT}} are failing on the CI,
> so they should be investigated and fixed.
> {noformat}
> [ERROR] Errors:
> [ERROR]
> InfinispanRemoteAggregationRepositoryIT.checkAggregationFromOneRoute:60 »
> NoSuchMethod 'org.infinispan.client.hotrod.configuration.ConfigurationBuilder
> org.infinispan.client.hotrod.configuration.ConfigurationBuilder.read(org.infinispan.client.hotrod.configuration.Configuration)'
> [ERROR] InfinispanRemoteAggregationRepositoryOperationsIT.setupResources:59
> » NoSuchMethod
> 'org.infinispan.client.hotrod.configuration.ConfigurationBuilder
> org.infinispan.client.hotrod.configuration.ConfigurationBuilder.read(org.infinispan.client.hotrod.configuration.Configuration)'{noformat}
> NB: The same tests seem to pass on the main branch
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19985) camel-smooks - Add component for Smooks for EDI data mapping
[ https://issues.apache.org/jira/browse/CAMEL-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847671#comment-17847671 ] Claus Ibsen commented on CAMEL-19985: - https://github.com/smooks/smooks-camel-cartridge/issues/211 > camel-smooks - Add component for Smooks for EDI data mapping > > > Key: CAMEL-19985 > URL: https://issues.apache.org/jira/browse/CAMEL-19985 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 4.x > > > This project is now ASF2 licensed > https://github.com/smooks/smooks > We used to have a camel-smooks component (camel-extra) in v1 many years ago. > We should add this component again, so users can use smooks for EDI data > mapping -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18597) Make Circuit Breakers and friends observable
[ https://issues.apache.org/jira/browse/CAMEL-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18597: Fix Version/s: Future > Make Circuit Breakers and friends observable > > > Key: CAMEL-18597 > URL: https://issues.apache.org/jira/browse/CAMEL-18597 > Project: Camel > Issue Type: New Feature > Components: camel-micrometer >Reporter: Marco Bungart >Priority: Minor > Fix For: Future > > > I would like to be able to monitor the state of my Circuit Breakers, as well > as related elements, e.g. ThrottlingExceptionRoutePolicy. > Thus, the state of such components should be exported in a standardized > manner (e.g. through micrometer), so I can automate monitoring and altering. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18383) camel-platform-http-vertx: Add option to run route processing on IO threads
[ https://issues.apache.org/jira/browse/CAMEL-18383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847655#comment-17847655 ] Claus Ibsen commented on CAMEL-18383: - Hmm I wonder if you want to do this per route, as setting this globally only would be to coarse grained from platform-http:foo?blocking=false from platform-http:bar > camel-platform-http-vertx: Add option to run route processing on IO threads > --- > > Key: CAMEL-18383 > URL: https://issues.apache.org/jira/browse/CAMEL-18383 > Project: Camel > Issue Type: Improvement > Components: camel-platform-http-vertx >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 4.x > > > Some more information in this issue: > https://github.com/apache/camel-quarkus/issues/3888 > There may be cases where you are not going to block the Vert.x event loop in > the Camel routing. Therefore, it may be desirable to not do this 'execute > blocking' logic: > https://github.com/apache/camel/blob/main/components/camel-platform-http-vertx/src/main/java/org/apache/camel/component/platform/http/vertx/VertxPlatformHttpConsumer.java#L168-L221 > And instead run the AsyncProcessor as per normal on an IO thread. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18280) Reuse AWS localstack docker image
[ https://issues.apache.org/jira/browse/CAMEL-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847654#comment-17847654 ] Claus Ibsen commented on CAMEL-18280: - Is this still the situation or does it run faster now ? > Reuse AWS localstack docker image > - > > Key: CAMEL-18280 > URL: https://issues.apache.org/jira/browse/CAMEL-18280 > Project: Camel > Issue Type: Improvement > Components: tests >Reporter: Federico Mariani >Priority: Minor > Labels: easy, help-wanted > Fix For: 4.x > > > AWS IT tests execution is slow mostly due to localstack docker image > restarts, can the docker image be reused via testcontainer? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17753) FailOverLoadBalancer does not Load Balance when sticky flag is set to true.
[ https://issues.apache.org/jira/browse/CAMEL-17753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17753. - Resolution: Won't Fix sticky will keep using the same last known good > FailOverLoadBalancer does not Load Balance when sticky flag is set to true. > --- > > Key: CAMEL-17753 > URL: https://issues.apache.org/jira/browse/CAMEL-17753 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 3.14.1 >Reporter: Vincenzo Galluccio >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17635) camel-yaml-dsl - Configuring bean properties should use key/value style
[ https://issues.apache.org/jira/browse/CAMEL-17635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17635. - Resolution: Won't Fix > camel-yaml-dsl - Configuring bean properties should use key/value style > --- > > Key: CAMEL-17635 > URL: https://issues.apache.org/jira/browse/CAMEL-17635 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Reporter: Claus Ibsen >Assignee: Radovan Netuka >Priority: Major > Fix For: Future > > > Yaml DSL has special beans configuration > https://camel.apache.org/components/next/others/yaml-dsl.html#_defining_beans > But the Camel DSL uses key/value style to be consistent across the DSLs (XML, > Java etc) in the route template locale bean and other places > Using array with key/value also makes this much easier for tooling as the XML > XSD and JSon Schema contract can know about this - otherwise its just > "object" which can be anything. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-15538) Provide a "Qiskit IBM Quantum Provider" Connector
[ https://issues.apache.org/jira/browse/CAMEL-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15538. - Resolution: Won't Fix > Provide a "Qiskit IBM Quantum Provider" Connector > - > > Key: CAMEL-15538 > URL: https://issues.apache.org/jira/browse/CAMEL-15538 > Project: Camel > Issue Type: New Feature >Reporter: Aurélien Pupier >Priority: Minor > > it will allow to use computing power of a Quantum computer. > - to launch job on a Quantum Computer > - to listen to result from the job on a Quantum computer > https://qiskit.org/documentation/apidoc/ibmq-provider.html > available library is written in Python so migth be quite some work > https://github.com/Qiskit/qiskit-ibmq-provider > or maybe it can be rewritten using directly the REST API for IBM Quantum > https://api.quantum-computing.ibm.com/v2/documentation.html?_ga=2.200951015.870923672.1604673144-1500770967.1598614684 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-14381) create a camel-mutiny component
[
https://issues.apache.org/jira/browse/CAMEL-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-14381.
-
Resolution: Information Provided
> create a camel-mutiny component
> ---
>
> Key: CAMEL-14381
> URL: https://issues.apache.org/jira/browse/CAMEL-14381
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: Future
>
>
> We should create a mutiny component, similar to camel-reactive-streams
> https://github.com/smallrye/smallrye-mutiny
> {code:java}
> CamelMutiny.on(context)
> .toMulti(servicenow().table("incident").max(100))
> .then(m -> doSomething(m))
> .await().indefinitely();
> {code}
> In Quarkus, we can nicely integrate camel into reactive messaging, like:
> {code:java}
> @Inject
> CamelMutiny mutiny;
> @Outgoing
> Multi fromEndpoint() {
> return mutiny.toMulti(servicenow().table("incident").max(100));
> }
> @Outgoing
> Multi fromEndpointURI() {
> return mutiny.toMulti("servicenow?table=incident");
> }
> @Incoming
> void toEndpoint(Multi items) {
> return mutiny.subscribeTo(items)
> .with(servicenow().table("incident").max(100).async());
> }
> @Incoming
> void toEndpointURI(Multi items) {
> return mutiny.subscribeTo(items)
> .with(s"servicenow?table=incident");
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-14381) create a camel-mutiny component
[
https://issues.apache.org/jira/browse/CAMEL-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847640#comment-17847640
]
Claus Ibsen commented on CAMEL-14381:
-
There is
https://smallrye.io/smallrye-reactive-messaging/smallrye-reactive-messaging/3.4/camel/camel.html
> create a camel-mutiny component
> ---
>
> Key: CAMEL-14381
> URL: https://issues.apache.org/jira/browse/CAMEL-14381
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: Future
>
>
> We should create a mutiny component, similar to camel-reactive-streams
> https://github.com/smallrye/smallrye-mutiny
> {code:java}
> CamelMutiny.on(context)
> .toMulti(servicenow().table("incident").max(100))
> .then(m -> doSomething(m))
> .await().indefinitely();
> {code}
> In Quarkus, we can nicely integrate camel into reactive messaging, like:
> {code:java}
> @Inject
> CamelMutiny mutiny;
> @Outgoing
> Multi fromEndpoint() {
> return mutiny.toMulti(servicenow().table("incident").max(100));
> }
> @Outgoing
> Multi fromEndpointURI() {
> return mutiny.toMulti("servicenow?table=incident");
> }
> @Incoming
> void toEndpoint(Multi items) {
> return mutiny.subscribeTo(items)
> .with(servicenow().table("incident").max(100).async());
> }
> @Incoming
> void toEndpointURI(Multi items) {
> return mutiny.subscribeTo(items)
> .with(s"servicenow?table=incident");
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20775) camel-hashicorp-vault - configure multiple engines
[
https://issues.apache.org/jira/browse/CAMEL-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20775:
Fix Version/s: 4.x
> camel-hashicorp-vault - configure multiple engines
> --
>
> Key: CAMEL-20775
> URL: https://issues.apache.org/jira/browse/CAMEL-20775
> Project: Camel
> Issue Type: Improvement
>Reporter: Federico Mariani
>Priority: Major
> Fix For: 4.x
>
>
> Currently, only one engine can be (easily) configured in the
> camel-hashicorp-vault component.
> It would be nice to configure the engine ala
> \{{hashicorp:engine:path/to/secret}} so that multiple engines can be used in
> the same application. for example, key/value store engine and pki store
> engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20775) camel-hashicorp-vault - configure multiple engines
[
https://issues.apache.org/jira/browse/CAMEL-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20775:
Component/s: camel-hashicorp-vault
> camel-hashicorp-vault - configure multiple engines
> --
>
> Key: CAMEL-20775
> URL: https://issues.apache.org/jira/browse/CAMEL-20775
> Project: Camel
> Issue Type: Improvement
> Components: camel-hashicorp-vault
>Reporter: Federico Mariani
>Priority: Major
> Fix For: 4.x
>
>
> Currently, only one engine can be (easily) configured in the
> camel-hashicorp-vault component.
> It would be nice to configure the engine ala
> \{{hashicorp:engine:path/to/secret}} so that multiple engines can be used in
> the same application. for example, key/value store engine and pki store
> engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847639#comment-17847639
]
Claus Ibsen commented on CAMEL-20786:
-
I put together an example using base64 properties function (instead of azure)
and it works in jbang and also in CSB (see attached zip file)
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
> Attachments: sb-props.zip
>
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20786:
Attachment: sb-props.zip
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
> Attachments: sb-props.zip
>
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20788) Use another protobuf-maven-plugin
Claus Ibsen created CAMEL-20788: --- Summary: Use another protobuf-maven-plugin Key: CAMEL-20788 URL: https://issues.apache.org/jira/browse/CAMEL-20788 Project: Camel Issue Type: Dependency upgrade Components: camel-salesforce Reporter: Claus Ibsen Fix For: 4.x The [https://www.xolstice.org/protobuf-maven-plugin] is not maintained anymore and last release is from 2018. We can use this instead [https://github.com/ascopes/protobuf-maven-plugin] -- This message was sent by Atlassian Jira (v8.20.10#820010)
