[jira] [Reopened] (CAMEL-18104) camel-core: provide a byte[] to Double Integer .... converter
[ https://issues.apache.org/jira/browse/CAMEL-18104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-18104: - There is a test failure in camel-kafka - that was impacted by this > camel-core: provide a byte[] to Double Integer converter > - > > Key: CAMEL-18104 > URL: https://issues.apache.org/jira/browse/CAMEL-18104 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Andrea Tarocchi >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.17.0 > > > for all the types that have a from string converter would be nice to provide > an alternative that from byte[] converts to string and from string to the > type basically cascading byte[] to string converter and string to type > converter. > It is useful for all the conversions in headers coming from kafka topics > since they usually come as byte[] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18127) camel-resume-api: adapter auto-configuration
[ https://issues.apache.org/jira/browse/CAMEL-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18127: - Description: Currently, in order to use the resume API, the integrations have to declare [adapters|https://camel.apache.org/components/next/eips/resume-strategies.html#_the_resume_adapter] that are [specific to the component and to the underlying offset data type|https://github.com/apache/camel-examples/blob/a33476ae644358b54cd11c93d2982ce0b0f36428/examples/resume-api/resume-api-fileset/src/main/java/org/apache/camel/example/resume/fileset/main/MainApp.java#L67-L68]. Not only this is error prone, but it also makes harder to use in scenarios like in Camel K or to use it in a declarative format (i.e.: YAML). The adapters used by each component should be, somehow, auto-configurable. The code on the components already have much of the information needed to setup the adapters on each component, so this can be leveraged. was: Currently, in order to use the resume API, the integrations have to declare adapters that are [specific to the component and to the underlying offset data type|https://github.com/apache/camel-examples/blob/a33476ae644358b54cd11c93d2982ce0b0f36428/examples/resume-api/resume-api-fileset/src/main/java/org/apache/camel/example/resume/fileset/main/MainApp.java#L67-L68]. Not only this is error prone, but it also makes harder to use in scenarios like in Camel K or to use it in a declarative format (i.e.: YAML). The adapters used by each component should be, somehow, auto-configurable. The code on the components already have much of the information needed to setup the adapters on each component, so this can be leveraged. > camel-resume-api: adapter auto-configuration > - > > Key: CAMEL-18127 > URL: https://issues.apache.org/jira/browse/CAMEL-18127 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.0 > > > Currently, in order to use the resume API, the integrations have to declare > [adapters|https://camel.apache.org/components/next/eips/resume-strategies.html#_the_resume_adapter] > that are [specific to the component and to the underlying offset data > type|https://github.com/apache/camel-examples/blob/a33476ae644358b54cd11c93d2982ce0b0f36428/examples/resume-api/resume-api-fileset/src/main/java/org/apache/camel/example/resume/fileset/main/MainApp.java#L67-L68]. > Not only this is error prone, but it also makes harder to use in scenarios > like in Camel K or to use it in a declarative format (i.e.: YAML). > > The adapters used by each component should be, somehow, auto-configurable. > > The code on the components already have much of the information needed to > setup the adapters on each component, so this can be leveraged. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18127) camel-resume-api: adapter auto-configuration
[ https://issues.apache.org/jira/browse/CAMEL-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18127: - Description: Currently, in order to use the resume API, the integrations have to declare adapters that are [specific to the component and to the underlying offset data type|https://github.com/apache/camel-examples/blob/a33476ae644358b54cd11c93d2982ce0b0f36428/examples/resume-api/resume-api-fileset/src/main/java/org/apache/camel/example/resume/fileset/main/MainApp.java#L67-L68]. Not only this is error prone, but it also makes harder to use in scenarios like in Camel K or to use it in a declarative format (i.e.: YAML). The adapters used by each component should be, somehow, auto-configurable. The code on the components already have much of the information needed to setup the adapters on each component, so this can be leveraged. was:The adapters used by each component should be, somehow, auto-configurable. This is necessary to make usage in Camel K easier. > camel-resume-api: adapter auto-configuration > - > > Key: CAMEL-18127 > URL: https://issues.apache.org/jira/browse/CAMEL-18127 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.0 > > > Currently, in order to use the resume API, the integrations have to declare > adapters that are [specific to the component and to the underlying offset > data > type|https://github.com/apache/camel-examples/blob/a33476ae644358b54cd11c93d2982ce0b0f36428/examples/resume-api/resume-api-fileset/src/main/java/org/apache/camel/example/resume/fileset/main/MainApp.java#L67-L68]. > Not only this is error prone, but it also makes harder to use in scenarios > like in Camel K or to use it in a declarative format (i.e.: YAML). > > The adapters used by each component should be, somehow, auto-configurable. > > The code on the components already have much of the information needed to > setup the adapters on each component, so this can be leveraged. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18128) camel-resume-api: resume endpoint self-configuration
Otavio Rodolfo Piske created CAMEL-18128: Summary: camel-resume-api: resume endpoint self-configuration Key: CAMEL-18128 URL: https://issues.apache.org/jira/browse/CAMEL-18128 Project: Camel Issue Type: Task Components: camel-resume-api Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Fix For: 3.18.0 Although the current way of configuring the resume strategies is flexible, it makes it very hard to work with it if we need to do so in a declarative way (i.e.: from a YAML file). Currently, every integration has to setup the connection parameters to the strategy accordingly (i.e.: [like we do in the example|https://github.com/apache/camel-examples/blob/a33476ae644358b54cd11c93d2982ce0b0f36428/examples/resume-api/resume-api-fileset/src/main/java/org/apache/camel/example/resume/fileset/main/MainApp.java#L56-L65]) We need to find a way to have the strategies self configure themselves based on the information they have available (i.e.: the component where they are being used, the resume adapters and the cache instances). For more complex scenarios, we need to provide a way to let integrations configure them with the same flexibility as there is at the moment. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (CAMEL-18111) Add support for private endpoint and custom DNS for Azure blob component
[ https://issues.apache.org/jira/browse/CAMEL-18111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Veillette closed CAMEL-18111. -- Resolution: Not A Problem After further investigation, the use of custom domain still remain unsupported by the component, but private end points work just fine. When using private endpoints, MS Azure remaps "xyz.blob.core.windows.net" as an alias to "xyz.privatelink.blob.core.windows.net" from inside the private network. In addition, the certificate is only issued for the public DNS entry anyway, which is an alias to the private DNS. So we can't use the "xyz.privatelink.blob.core.windows.net" domain. > Add support for private endpoint and custom DNS for Azure blob component > > > Key: CAMEL-18111 > URL: https://issues.apache.org/jira/browse/CAMEL-18111 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.16.0 >Reporter: Hugo Veillette >Priority: Major > Labels: azureblob, security > > Hi, the current implementation of the Azure Blob component forces to use the > public Microsoft endpoint when defined via configuration. > This limitation prevents the component to be used in conjunction with MS > [private endpoint > |https://docs.microsoft.com/en-us/azure/storage/common/storage-private-endpoints] > (which use a different DNS) or to use a custom DNS. > See > [BlobClientFactory.java#L2|https://github.com/apache/camel/blob/1e1b0bfa8393fae16ebc44cd1a8f9ac595db26ed/components/camel-azure/camel-azure-storage-blob/src/main/java/org/apache/camel/component/azure/storage/blob/client/BlobClientFactory.java#L29] > > The current issue is a feature request to remove the current limitation, > effectively enabling the usage of private-endpoints and custom DNS. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18123) Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header
[ https://issues.apache.org/jira/browse/CAMEL-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18123. - Resolution: Fixed > Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header > --- > > Key: CAMEL-18123 > URL: https://issues.apache.org/jira/browse/CAMEL-18123 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.14.4, 3.17.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > Fix For: 3.14.4, 3.18.0 > > > Both PurheQueu and DrleteQueue operations work only if header > SQS_QUEUE_PREFIX is filled with any value. This header is not required at all > (https://github.com/apache/camel/blob/64c1fbdf0c3dd130ce21a6e1cd0cd97c0d1e3473/components/camel-aws/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Producer.java#L184) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18123) Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header
[ https://issues.apache.org/jira/browse/CAMEL-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18123: Priority: Minor (was: Major) > Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header > --- > > Key: CAMEL-18123 > URL: https://issues.apache.org/jira/browse/CAMEL-18123 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.14.4, 3.17.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > Fix For: 3.14.4, 3.18.0 > > > Both PurheQueu and DrleteQueue operations work only if header > SQS_QUEUE_PREFIX is filled with any value. This header is not required at all > (https://github.com/apache/camel/blob/64c1fbdf0c3dd130ce21a6e1cd0cd97c0d1e3473/components/camel-aws/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Producer.java#L184) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18118) camel-jbang - Linux terminal scripting using pipes
[ https://issues.apache.org/jira/browse/CAMEL-18118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18118. - Resolution: Fixed > camel-jbang - Linux terminal scripting using pipes > -- > > Key: CAMEL-18118 > URL: https://issues.apache.org/jira/browse/CAMEL-18118 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > So you can use a camel route in linux scripting. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-18118) camel-jbang - Linux terminal scripting using pipes
[ https://issues.apache.org/jira/browse/CAMEL-18118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538129#comment-17538129 ] Claus Ibsen edited comment on CAMEL-18118 at 5/18/22 5:14 PM: -- TODO: logging to file *DONE* TODO: stream:in to read entire content (eg group=all) *DONE* was (Author: davsclaus): TODO: logging to file *DONE* TODO: stream:in to read entire content (eg group=all) > camel-jbang - Linux terminal scripting using pipes > -- > > Key: CAMEL-18118 > URL: https://issues.apache.org/jira/browse/CAMEL-18118 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > So you can use a camel route in linux scripting. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18124) camel-stream - stream:in to read entire content as byte[]
[ https://issues.apache.org/jira/browse/CAMEL-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18124. - Resolution: Fixed > camel-stream - stream:in to read entire content as byte[] > - > > Key: CAMEL-18124 > URL: https://issues.apache.org/jira/browse/CAMEL-18124 > Project: Camel > Issue Type: New Feature > Components: camel-stream >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > So you can stream in some content like a binary file, or json file etc and > want to load its entire content using linux terminal pipes. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18126) camel-resume-api: investigate support with split EIP
[
https://issues.apache.org/jira/browse/CAMEL-18126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-18126:
-
Description:
For a given route configured as:
{code:java}
from().resumable().split(body()...).to(){code}
The API should, somehow, track the offset of the splitted parts so that a
resume operation starts from the last processing point.
was:
For a given route configured as:
from().resumable().split(body()...).to()
The API should, somehow, track the offset of the splitted parts so that a
resume operation starts from the last processing point.
> camel-resume-api: investigate support with split EIP
>
>
> Key: CAMEL-18126
> URL: https://issues.apache.org/jira/browse/CAMEL-18126
> Project: Camel
> Issue Type: Task
> Components: camel-resume-api
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.18.0
>
>
> For a given route configured as:
> {code:java}
> from().resumable().split(body()...).to(){code}
> The API should, somehow, track the offset of the splitted parts so that a
> resume operation starts from the last processing point.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CAMEL-18126) camel-resume-api: investigate support with split EIP
[ https://issues.apache.org/jira/browse/CAMEL-18126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18126: - Description: For a given route configured as: from().resumable().split(body()...).to() The API should, somehow, track the offset of the splitted parts so that a resume operation starts from the last processing point. > camel-resume-api: investigate support with split EIP > > > Key: CAMEL-18126 > URL: https://issues.apache.org/jira/browse/CAMEL-18126 > Project: Camel > Issue Type: Task > Components: camel-resume-api >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.0 > > > For a given route configured as: > from().resumable().split(body()...).to() > The API should, somehow, track the offset of the splitted parts so that a > resume operation starts from the last processing point. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18127) camel-resume-api: adapter auto-configuration
Otavio Rodolfo Piske created CAMEL-18127: Summary: camel-resume-api: adapter auto-configuration Key: CAMEL-18127 URL: https://issues.apache.org/jira/browse/CAMEL-18127 Project: Camel Issue Type: Task Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske The adapters used by each component should be, somehow, auto-configurable. This is necessary to make usage in Camel K easier. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18127) camel-resume-api: adapter auto-configuration
[ https://issues.apache.org/jira/browse/CAMEL-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18127: - Fix Version/s: 3.18.0 > camel-resume-api: adapter auto-configuration > - > > Key: CAMEL-18127 > URL: https://issues.apache.org/jira/browse/CAMEL-18127 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.0 > > > The adapters used by each component should be, somehow, auto-configurable. > This is necessary to make usage in Camel K easier. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18125) camel-resume-api: improvements and additional support
[ https://issues.apache.org/jira/browse/CAMEL-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18125: - Summary: camel-resume-api: improvements and additional support (was: CLONE - camel-resume-api: improvements and additional support) > camel-resume-api: improvements and additional support > - > > Key: CAMEL-18125 > URL: https://issues.apache.org/jira/browse/CAMEL-18125 > Project: Camel > Issue Type: New Feature >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.0 > > > This is a tracking ticket for subsequent improvements for the Resume API v2 > work. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18126) camel-resume-api: investigate support with split EIP
Otavio Rodolfo Piske created CAMEL-18126: Summary: camel-resume-api: investigate support with split EIP Key: CAMEL-18126 URL: https://issues.apache.org/jira/browse/CAMEL-18126 Project: Camel Issue Type: Task Components: camel-resume-api Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18125) CLONE - camel-resume-api: improvements and additional support
[ https://issues.apache.org/jira/browse/CAMEL-18125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18125: - Fix Version/s: 3.18.0 (was: 3.17.0) > CLONE - camel-resume-api: improvements and additional support > - > > Key: CAMEL-18125 > URL: https://issues.apache.org/jira/browse/CAMEL-18125 > Project: Camel > Issue Type: New Feature >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.0 > > > This is a tracking ticket for subsequent improvements for the Resume API v2 > work. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17963) camel-resume-api: add support for more components
[ https://issues.apache.org/jira/browse/CAMEL-17963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538894#comment-17538894 ] Otavio Rodolfo Piske commented on CAMEL-17963: -- To investigate: aws-s3 > camel-resume-api: add support for more components > - > > Key: CAMEL-17963 > URL: https://issues.apache.org/jira/browse/CAMEL-17963 > Project: Camel > Issue Type: Task > Components: camel-resume-api >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.18.0 > > > Increase component coverage for the resume API -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18125) CLONE - camel-resume-api: improvements and additional support
Otavio Rodolfo Piske created CAMEL-18125: Summary: CLONE - camel-resume-api: improvements and additional support Key: CAMEL-18125 URL: https://issues.apache.org/jira/browse/CAMEL-18125 Project: Camel Issue Type: New Feature Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Fix For: 3.17.0 This is a tracking ticket for subsequent improvements for the Resume API v2 work. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-14079) Upgrade to Jetty 9.4.21.v20190926
[ https://issues.apache.org/jira/browse/CAMEL-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14079. - Resolution: Fixed > Upgrade to Jetty 9.4.21.v20190926 > - > > Key: CAMEL-14079 > URL: https://issues.apache.org/jira/browse/CAMEL-14079 > Project: Camel > Issue Type: Task > Components: camel-jetty >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-18097) camel-aws - Unable to override uri-endpoint-override override-endpoint options for STS
[
https://issues.apache.org/jira/browse/CAMEL-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538808#comment-17538808
]
Andrea Cosentino commented on CAMEL-18097:
--
It is working as expected, so it seems to be something on your side.
> camel-aws - Unable to override uri-endpoint-override override-endpoint
> options for STS
> --
>
> Key: CAMEL-18097
> URL: https://issues.apache.org/jira/browse/CAMEL-18097
> Project: Camel
> Issue Type: Bug
> Components: camel-aws, camel-spring-boot
>Affects Versions: 3.14.2
>Reporter: Oreste Creolese
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.18.0
>
>
> Our goal is to no longer access AWS endpoints via a custom proxy but to
> access them via VPC endpoints from AWS. To make this work in our secured
> network we use our own VPC endpoints which we configure with the option:
> uri-endpoint-override (string) and override-endpoint (boolean). Now the
> problem is that the options are not used at all and the application always
> uses the default endpoints which have no access in our network. Because of
> this the STS component can't execute a HTTP request.
> *And in the console the following error message appears:*
> {code:java}
>
> Unable to execute HTTP request: Connect to sts.eu-central-1.amazonaws.com:443
> [sts.eu-central-1.amazonaws.com/54.239.54.207] failed: Connect timed out,
> ContainerCredentialsProvider(): Cannot fetch credentials from container -
> neither AWS_CONTAINER_CREDENTIALS_FULL_URI or
> AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variables are set
> {code}
> As taken from the error message, the default endpoint
> sts.eu-central-1.amazonaws.com:443 is used.
> *This is how our application.properties looks in which the options are set:*
> {code:java}
> camel.component.aws2-sts.override-endpoint=true
> camel.component.aws2-sts.uri-endpoint-override=https://vpce-???-???.sts.eu
> central1.vpce.amazonaws.com{code}
> *We are using the following versions:*
> * Apache Camel 3.14.2
> * Spring Boot 2.5.10
> *Dependencies*
> {code:java}
>
> 14
> 3.14.2
> 2.5.10
>
>
>
> org.springframework.boot
> spring-boot-starter-test
> test
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-s3-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-sts-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
> org.apache.camel
> camel-jetty
> ${camel.version}
>
>
> org.apache.camel
> camel-json-validator
> ${camel.version}
>
> {code}
> *Info* With ticket CAMEL-16171 , Camel added the usage of
> uri-endpoint-override and override-endpoint options attributes for all AWS
> components among others for STS.
> Do you have any idea why the options are not overwritten? Thanks a lot for
> your help!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-18097) camel-aws - Unable to override uri-endpoint-override override-endpoint options for STS
[
https://issues.apache.org/jira/browse/CAMEL-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538807#comment-17538807
]
Andrea Cosentino edited comment on CAMEL-18097 at 5/18/22 12:43 PM:
With an xml like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
org.apache.camel.springboot.example
examples
3.17.0-SNAPSHOT
camel-example-spring-boot-aws2-sts
Camel SB Examples :: AWS2 STS
An example showing the Camel AWS2 STS component with Spring
Boot
Cloud
org.springframework.boot
spring-boot-dependencies
2.6.4
pom
import
org.apache.camel.springboot
camel-spring-boot-bom
3.14.2
pom
import
org.apache.camel.springboot
camel-spring-boot-starter
org.apache.camel.springboot
camel-aws2-sts-starter
org.apache.camel.springboot
camel-timer-starter
org.springframework.boot
spring-boot-maven-plugin
2.6.4
repackage
{code}
An application.properties like this:
{code:java}
camel.component.aws2-sts.accessKey=
camel.component.aws2-sts.secretKey=y
camel.component.aws2-sts.region=eu-central-1
camel.springboot.main-run-controller=true
logging.config=classpath:logback.xml
camel.component.aws2-sts.override-endpoint=true
camel.component.aws2-sts.uri-endpoint-override=https://vpce-pippo-pluto.sts.eu.central1.vpce.amazonaws.com
{code}
and a route like:
{code:java}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.camel.example.springboot.aws2sts;
import org.apache.camel.builder.RouteBuilder;
import org.springframework.stereotype.Component;
@Component
public class CamelRoute extends RouteBuilder {
@Override
public void configure() throws Exception {
from("timer://tick?period=1000")
.to("aws2-sts://label?operation=getSessionToken");
}
}
{code}
I'm getting the following error:
{code:java}
[INFO] --- spring-boot-maven-plugin:2.6.4:run (default-cli) @
camel-example-spring-boot-aws2-sts ---
[INFO] Attaching agents: []
. ___ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' || .__|_| |_|_| |_\__, | / / / /
=|_|==|___/=/_/_/_/
:: Spring Boot ::(v2.6.4)
14:38:40.132 [main ] INFO .springboot.aws2s3.Application - Starting
Application using Java 11.0.15 on ghost with PID 31495
(/home/oscerd/workspace/apache-camel/camel-spring-boot-examples/aws2-sts/target/classes
started by oscerd in
/home/oscerd/workspace/apache-camel/camel-spring-boot-examples/aws2-sts)
14:38:40.133 [main ] INFO .springboot.aws2s3.Application - No active
profile set, falling back to 1 default profile: "default"
14:38:41.242 [main ] INFO lSpringBootApplicationListener - Starting
CamelMainRunController to ensure the main thread keeps running
14:38:41.248 [main ] INFO pl.engine.AbstractCamelContext - Routes
startup (total:1 started:1)
14:38:41.249 [main ] INFO pl.engine.AbstractCamelContext -
Started route1 (timer://tick)
14:38:41.249 [main ] INFO pl.engine.AbstractCamelContext - Apache
Camel 3.14.2 (camel-1) started in 328ms (build:20ms init:75ms start:233ms)
14:38:41.252 [main ] INFO .springboot.aws2s3.Application - Started
Application in
[jira] [Commented] (CAMEL-18097) camel-aws - Unable to override uri-endpoint-override override-endpoint options for STS
[
https://issues.apache.org/jira/browse/CAMEL-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538807#comment-17538807
]
Andrea Cosentino commented on CAMEL-18097:
--
With an xml like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
org.apache.camel.springboot.example
examples
3.17.0-SNAPSHOT
camel-example-spring-boot-aws2-sts
Camel SB Examples :: AWS2 STS
An example showing the Camel AWS2 STS component with Spring
Boot
Cloud
org.springframework.boot
spring-boot-dependencies
2.6.4
pom
import
org.apache.camel.springboot
camel-spring-boot-bom
3.14.2
pom
import
org.apache.camel.springboot
camel-spring-boot-starter
org.apache.camel.springboot
camel-aws2-sts-starter
org.apache.camel.springboot
camel-timer-starter
org.springframework.boot
spring-boot-maven-plugin
2.6.4
repackage
{code}
An application.properties like this:
{code:java}
camel.component.aws2-sts.accessKey=
camel.component.aws2-sts.secretKey=y
camel.component.aws2-sts.region=eu-central-1
camel.springboot.main-run-controller=true
logging.config=classpath:logback.xml
camel.component.aws2-sts.override-endpoint=true
camel.component.aws2-sts.uri-endpoint-override=https://vpce-pippo-pluto.sts.eu.central1.vpce.amazonaws.com
{code}
and a route like:
{code:java}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.camel.example.springboot.aws2sts;
import org.apache.camel.builder.RouteBuilder;
import org.springframework.stereotype.Component;
@Component
public class CamelRoute extends RouteBuilder {
@Override
public void configure() throws Exception {
from("timer://tick?period=1000")
.to("aws2-sts://label?operation=getSessionToken");
}
}
{code}
I'm getting the following error:
{code:java}
[INFO] --- spring-boot-maven-plugin:2.6.4:run (default-cli) @
camel-example-spring-boot-aws2-sts ---
[INFO] Attaching agents: []
. ___ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' || .__|_| |_|_| |_\__, | / / / /
=|_|==|___/=/_/_/_/
:: Spring Boot ::(v2.6.4)
14:38:40.132 [main ] INFO .springboot.aws2s3.Application - Starting
Application using Java 11.0.15 on ghost with PID 31495
(/home/oscerd/workspace/apache-camel/camel-spring-boot-examples/aws2-sts/target/classes
started by oscerd in
/home/oscerd/workspace/apache-camel/camel-spring-boot-examples/aws2-sts)
14:38:40.133 [main ] INFO .springboot.aws2s3.Application - No active
profile set, falling back to 1 default profile: "default"
14:38:41.242 [main ] INFO lSpringBootApplicationListener - Starting
CamelMainRunController to ensure the main thread keeps running
14:38:41.248 [main ] INFO pl.engine.AbstractCamelContext - Routes
startup (total:1 started:1)
14:38:41.249 [main ] INFO pl.engine.AbstractCamelContext -
Started route1 (timer://tick)
14:38:41.249 [main ] INFO pl.engine.AbstractCamelContext - Apache
Camel 3.14.2 (camel-1) started in 328ms (build:20ms init:75ms start:233ms)
14:38:41.252 [main ] INFO .springboot.aws2s3.Application - Started
Application in 1.316 seconds (JVM running for 1.623)
14:38:52.603 [ -
[jira] [Commented] (CAMEL-18097) camel-aws - Unable to override uri-endpoint-override override-endpoint options for STS
[
https://issues.apache.org/jira/browse/CAMEL-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538803#comment-17538803
]
Andrea Cosentino commented on CAMEL-18097:
--
Also if your runtime is Spring boot you should use also camel-jetty-starter and
json-validator-starter. Don't mix up plain components and Spring Boot
components.
> camel-aws - Unable to override uri-endpoint-override override-endpoint
> options for STS
> --
>
> Key: CAMEL-18097
> URL: https://issues.apache.org/jira/browse/CAMEL-18097
> Project: Camel
> Issue Type: Bug
> Components: camel-aws, camel-spring-boot
>Affects Versions: 3.14.2
>Reporter: Oreste Creolese
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.18.0
>
>
> Our goal is to no longer access AWS endpoints via a custom proxy but to
> access them via VPC endpoints from AWS. To make this work in our secured
> network we use our own VPC endpoints which we configure with the option:
> uri-endpoint-override (string) and override-endpoint (boolean). Now the
> problem is that the options are not used at all and the application always
> uses the default endpoints which have no access in our network. Because of
> this the STS component can't execute a HTTP request.
> *And in the console the following error message appears:*
> {code:java}
>
> Unable to execute HTTP request: Connect to sts.eu-central-1.amazonaws.com:443
> [sts.eu-central-1.amazonaws.com/54.239.54.207] failed: Connect timed out,
> ContainerCredentialsProvider(): Cannot fetch credentials from container -
> neither AWS_CONTAINER_CREDENTIALS_FULL_URI or
> AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variables are set
> {code}
> As taken from the error message, the default endpoint
> sts.eu-central-1.amazonaws.com:443 is used.
> *This is how our application.properties looks in which the options are set:*
> {code:java}
> camel.component.aws2-sts.override-endpoint=true
> camel.component.aws2-sts.uri-endpoint-override=https://vpce-???-???.sts.eu
> central1.vpce.amazonaws.com{code}
> *We are using the following versions:*
> * Apache Camel 3.14.2
> * Spring Boot 2.5.10
> *Dependencies*
> {code:java}
>
> 14
> 3.14.2
> 2.5.10
>
>
>
> org.springframework.boot
> spring-boot-starter-test
> test
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-s3-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-sts-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
> org.apache.camel
> camel-jetty
> ${camel.version}
>
>
> org.apache.camel
> camel-json-validator
> ${camel.version}
>
> {code}
> *Info* With ticket CAMEL-16171 , Camel added the usage of
> uri-endpoint-override and override-endpoint options attributes for all AWS
> components among others for STS.
> Do you have any idea why the options are not overwritten? Thanks a lot for
> your help!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-18097) camel-aws - Unable to override uri-endpoint-override override-endpoint options for STS
[
https://issues.apache.org/jira/browse/CAMEL-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538796#comment-17538796
]
Andrea Cosentino commented on CAMEL-18097:
--
Another important point. Camel 3.14.2 use Spring Boot 2.6.4 while you're
pointing 2.5.10. Can you please test with the correct SB version?
> camel-aws - Unable to override uri-endpoint-override override-endpoint
> options for STS
> --
>
> Key: CAMEL-18097
> URL: https://issues.apache.org/jira/browse/CAMEL-18097
> Project: Camel
> Issue Type: Bug
> Components: camel-aws, camel-spring-boot
>Affects Versions: 3.14.2
>Reporter: Oreste Creolese
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.18.0
>
>
> Our goal is to no longer access AWS endpoints via a custom proxy but to
> access them via VPC endpoints from AWS. To make this work in our secured
> network we use our own VPC endpoints which we configure with the option:
> uri-endpoint-override (string) and override-endpoint (boolean). Now the
> problem is that the options are not used at all and the application always
> uses the default endpoints which have no access in our network. Because of
> this the STS component can't execute a HTTP request.
> *And in the console the following error message appears:*
> {code:java}
>
> Unable to execute HTTP request: Connect to sts.eu-central-1.amazonaws.com:443
> [sts.eu-central-1.amazonaws.com/54.239.54.207] failed: Connect timed out,
> ContainerCredentialsProvider(): Cannot fetch credentials from container -
> neither AWS_CONTAINER_CREDENTIALS_FULL_URI or
> AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variables are set
> {code}
> As taken from the error message, the default endpoint
> sts.eu-central-1.amazonaws.com:443 is used.
> *This is how our application.properties looks in which the options are set:*
> {code:java}
> camel.component.aws2-sts.override-endpoint=true
> camel.component.aws2-sts.uri-endpoint-override=https://vpce-???-???.sts.eu
> central1.vpce.amazonaws.com{code}
> *We are using the following versions:*
> * Apache Camel 3.14.2
> * Spring Boot 2.5.10
> *Dependencies*
> {code:java}
>
> 14
> 3.14.2
> 2.5.10
>
>
>
> org.springframework.boot
> spring-boot-starter-test
> test
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-s3-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-sts-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
> org.apache.camel
> camel-jetty
> ${camel.version}
>
>
> org.apache.camel
> camel-json-validator
> ${camel.version}
>
> {code}
> *Info* With ticket CAMEL-16171 , Camel added the usage of
> uri-endpoint-override and override-endpoint options attributes for all AWS
> components among others for STS.
> Do you have any idea why the options are not overwritten? Thanks a lot for
> your help!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CAMEL-18097) camel-aws - Unable to override uri-endpoint-override override-endpoint options for STS
[
https://issues.apache.org/jira/browse/CAMEL-18097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538793#comment-17538793
]
Andrea Cosentino commented on CAMEL-18097:
--
Can you please show the route and your full configuration?
> camel-aws - Unable to override uri-endpoint-override override-endpoint
> options for STS
> --
>
> Key: CAMEL-18097
> URL: https://issues.apache.org/jira/browse/CAMEL-18097
> Project: Camel
> Issue Type: Bug
> Components: camel-aws, camel-spring-boot
>Affects Versions: 3.14.2
>Reporter: Oreste Creolese
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.18.0
>
>
> Our goal is to no longer access AWS endpoints via a custom proxy but to
> access them via VPC endpoints from AWS. To make this work in our secured
> network we use our own VPC endpoints which we configure with the option:
> uri-endpoint-override (string) and override-endpoint (boolean). Now the
> problem is that the options are not used at all and the application always
> uses the default endpoints which have no access in our network. Because of
> this the STS component can't execute a HTTP request.
> *And in the console the following error message appears:*
> {code:java}
>
> Unable to execute HTTP request: Connect to sts.eu-central-1.amazonaws.com:443
> [sts.eu-central-1.amazonaws.com/54.239.54.207] failed: Connect timed out,
> ContainerCredentialsProvider(): Cannot fetch credentials from container -
> neither AWS_CONTAINER_CREDENTIALS_FULL_URI or
> AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variables are set
> {code}
> As taken from the error message, the default endpoint
> sts.eu-central-1.amazonaws.com:443 is used.
> *This is how our application.properties looks in which the options are set:*
> {code:java}
> camel.component.aws2-sts.override-endpoint=true
> camel.component.aws2-sts.uri-endpoint-override=https://vpce-???-???.sts.eu
> central1.vpce.amazonaws.com{code}
> *We are using the following versions:*
> * Apache Camel 3.14.2
> * Spring Boot 2.5.10
> *Dependencies*
> {code:java}
>
> 14
> 3.14.2
> 2.5.10
>
>
>
> org.springframework.boot
> spring-boot-starter-test
> test
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-s3-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
>
> org.apache.camel.springboot
> camel-aws2-sts-starter
>
>
> org.springframework.boot
> spring-boot-starter-logging
>
>
>
>
> org.apache.camel
> camel-jetty
> ${camel.version}
>
>
> org.apache.camel
> camel-json-validator
> ${camel.version}
>
> {code}
> *Info* With ticket CAMEL-16171 , Camel added the usage of
> uri-endpoint-override and override-endpoint options attributes for all AWS
> components among others for STS.
> Do you have any idea why the options are not overwritten? Thanks a lot for
> your help!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (CAMEL-18124) camel-stream - stream:in to read entire content as byte[]
Claus Ibsen created CAMEL-18124: --- Summary: camel-stream - stream:in to read entire content as byte[] Key: CAMEL-18124 URL: https://issues.apache.org/jira/browse/CAMEL-18124 Project: Camel Issue Type: New Feature Components: camel-stream Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.0 So you can stream in some content like a binary file, or json file etc and want to load its entire content using linux terminal pipes. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18123) Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header
[ https://issues.apache.org/jira/browse/CAMEL-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18123: Fix Version/s: 3.14.4 3.18.0 > Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header > --- > > Key: CAMEL-18123 > URL: https://issues.apache.org/jira/browse/CAMEL-18123 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.14.4, 3.17.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.14.4, 3.18.0 > > > Both PurheQueu and DrleteQueue operations work only if header > SQS_QUEUE_PREFIX is filled with any value. This header is not required at all > (https://github.com/apache/camel/blob/64c1fbdf0c3dd130ce21a6e1cd0cd97c0d1e3473/components/camel-aws/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Producer.java#L184) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-18118) camel-jbang - Linux terminal scripting using pipes
[ https://issues.apache.org/jira/browse/CAMEL-18118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538129#comment-17538129 ] Claus Ibsen edited comment on CAMEL-18118 at 5/18/22 12:11 PM: --- TODO: logging to file *DONE* TODO: stream:in to read entire content (eg group=all) was (Author: davsclaus): TODO: logging to file *DONE* TODO: CLI args as property placeholders instead of --prop=a=123 --prop=b=456 then you should be able to do ./myscript.java a=123 b=456 TODO: stream:in to read entire content (eg group=all) > camel-jbang - Linux terminal scripting using pipes > -- > > Key: CAMEL-18118 > URL: https://issues.apache.org/jira/browse/CAMEL-18118 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > So you can use a camel route in linux scripting. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18123) Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header
[ https://issues.apache.org/jira/browse/CAMEL-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek updated CAMEL-18123: -- Summary: Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header (was: Aws2-sqs: Operations PurgeQueue and DeleteQueueu requires unnecessary header) > Aws2-sqs: Operations PurgeQueue and DeleteQueue requires unnecessary header > --- > > Key: CAMEL-18123 > URL: https://issues.apache.org/jira/browse/CAMEL-18123 > Project: Camel > Issue Type: Bug > Components: camel-aws2 >Affects Versions: 3.14.4, 3.17.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Both PurheQueu and DrleteQueue operations work only if header > SQS_QUEUE_PREFIX is filled with any value. This header is not required at all > (https://github.com/apache/camel/blob/64c1fbdf0c3dd130ce21a6e1cd0cd97c0d1e3473/components/camel-aws/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Producer.java#L184) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18123) Aws2-sqs: Operations PurgeQueue and DeleteQueueu requires unnecessary header
Jiri Ondrusek created CAMEL-18123: - Summary: Aws2-sqs: Operations PurgeQueue and DeleteQueueu requires unnecessary header Key: CAMEL-18123 URL: https://issues.apache.org/jira/browse/CAMEL-18123 Project: Camel Issue Type: Bug Components: camel-aws2 Affects Versions: 3.14.4, 3.17.0 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek Both PurheQueu and DrleteQueue operations work only if header SQS_QUEUE_PREFIX is filled with any value. This header is not required at all (https://github.com/apache/camel/blob/64c1fbdf0c3dd130ce21a6e1cd0cd97c0d1e3473/components/camel-aws/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Producer.java#L184) -- This message was sent by Atlassian Jira (v8.20.7#820007)
