[jira] [Created] (CAMEL-18511) Camel-Azure-Key-Vault: Create a task looking for secrets update in Eventhubs
Andrea Cosentino created CAMEL-18511: Summary: Camel-Azure-Key-Vault: Create a task looking for secrets update in Eventhubs Key: CAMEL-18511 URL: https://issues.apache.org/jira/browse/CAMEL-18511 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18502) Support Secrets Reload from Vault/Cloud Service in camel-spring-boot - Google Secret Manager
[ https://issues.apache.org/jira/browse/CAMEL-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18502. -- Resolution: Fixed > Support Secrets Reload from Vault/Cloud Service in camel-spring-boot - Google > Secret Manager > > > Key: CAMEL-18502 > URL: https://issues.apache.org/jira/browse/CAMEL-18502 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18501) Camel-Google-Secret-Manager: Create a task looking for secrets update in PubSub
[ https://issues.apache.org/jira/browse/CAMEL-18501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18501. -- Resolution: Fixed > Camel-Google-Secret-Manager: Create a task looking for secrets update in > PubSub > --- > > Key: CAMEL-18501 > URL: https://issues.apache.org/jira/browse/CAMEL-18501 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18502) Support Secrets Reload from Vault/Cloud Service in camel-spring-boot - Google Secret Manager
Andrea Cosentino created CAMEL-18502: Summary: Support Secrets Reload from Vault/Cloud Service in camel-spring-boot - Google Secret Manager Key: CAMEL-18502 URL: https://issues.apache.org/jira/browse/CAMEL-18502 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18478) Support Secrets Reload from Vault/Cloud Service in camel-spring-boot - AWS Secrets Manager
[ https://issues.apache.org/jira/browse/CAMEL-18478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18478: - Summary: Support Secrets Reload from Vault/Cloud Service in camel-spring-boot - AWS Secrets Manager (was: Support Secrets Reload from Vault/Cloud Service in camel-spring-boot ) > Support Secrets Reload from Vault/Cloud Service in camel-spring-boot - AWS > Secrets Manager > -- > > Key: CAMEL-18478 > URL: https://issues.apache.org/jira/browse/CAMEL-18478 > Project: Camel > Issue Type: Sub-task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18501) Camel-Google-Secret-Manager: Create a task looking for secrets update in PubSub
Andrea Cosentino created CAMEL-18501: Summary: Camel-Google-Secret-Manager: Create a task looking for secrets update in PubSub Key: CAMEL-18501 URL: https://issues.apache.org/jira/browse/CAMEL-18501 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18498) Create a Camel AWS Event Ruler component
Andrea Cosentino created CAMEL-18498: Summary: Create a Camel AWS Event Ruler component Key: CAMEL-18498 URL: https://issues.apache.org/jira/browse/CAMEL-18498 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18466) Camel-AWS2-SQS: Move from ComponentVerifierExtension to HealtCheck
[ https://issues.apache.org/jira/browse/CAMEL-18466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18466. -- Resolution: Fixed > Camel-AWS2-SQS: Move from ComponentVerifierExtension to HealtCheck > -- > > Key: CAMEL-18466 > URL: https://issues.apache.org/jira/browse/CAMEL-18466 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18492) Enterprise Feature of Saxon is Disabled in Camel 3.x versions.
[
https://issues.apache.org/jira/browse/CAMEL-18492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602301#comment-17602301
]
Andrea Cosentino commented on CAMEL-18492:
--
So maybe we should make it configurable and set to true by default. [~davsclaus]
> Enterprise Feature of Saxon is Disabled in Camel 3.x versions.
> --
>
> Key: CAMEL-18492
> URL: https://issues.apache.org/jira/browse/CAMEL-18492
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon, camel-xslt
>Affects Versions: 3.0.0
>Reporter: Harish Annamalai
>Priority: Major
>
> Hi All,
> We use Camel-Saxon for one of our product. We use Saxon Enterprise Edition
> 9.9.1.6.
> We are migrating our product from camel 2.x to camel 3.x (2.24 to 3.15 to be
> exact).
> We use a paid feature of Saxon; Invoking *External Java Functions* in XSL
> Transformations.
> We also *Extension Functions,* which we pass to camel-xslt-saxon component.
> What we have observed in camel 3.x versions and above, In class
> {{{*}XsltSaxonEndpoint{*}.java}} During the registration of extension
> functions, at line 202, {{registerSaxonExtensionFunctions}} method of
> {{{*}XsltSaxonHelper{*}.java}} is called.
>
> In XsltSaxonHelper.class, the method,
> {{{}registerSaxonExtensionFunctions{}}}, at line 55, sets a feature of
> {*}XMLConstants.FEATURE_SECURE_PROCESSING{*}.
> Unfortunately, Setting this Feature disables the External Java Function
> calls.
> We checked in Camel 2.x versions, this Feature is not set and therefore the
> External Java Calls work fine.
>
> We see this as a bug - The Feature *XMLConstants.FEATURE_SECURE_PROCESSING*
> is being introduced in 3.x and breaks a paid/Enterprise feature of Saxon.
>
> Sample Code to test:
> {{import javax.xml.XMLConstants;}}
> {{import javax.xml.transform.Transformer;}}
> {{import javax.xml.transform.TransformerException;}}
> {{import javax.xml.transform.TransformerFactory;}}
> {{import javax.xml.transform.stream.StreamResult;}}
> {{import javax.xml.transform.stream.StreamSource;}}
> {{import java.io.File;}}
> {{public class SaxonTransformationTester {}}
> {{ public static void main(String[] args) throws TransformerException {}}
> {{ String foo_xml = "src/main/resources/in.xml"; // input xml}}
> {{ String foo_xsl = "src/main/resources/transf.xml"; // input xsl}}
> {{ EnterpriseTransformerFactory eef =
> SaxonEEConsumerFactory.getEnterpriseTransformerFactoryInstance();}}
> {{
> eef.getConfiguration().getConfigurationProperty(Feature.ALLOW_EXTERNAL_FUNCTIONS);}}
> {{ eef.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true); //This
> causes External Functions to break}}
> {{
> eef.getConfiguration().setConfigurationProperty("http://saxon.sf.net/feature/trace-external-functions;,
> false);}}
> {{ Transformer transformer = eef.newTransformer(new StreamSource(}}
> {{ new File(foo_xsl)));}}
> {{ transformer.transform(new StreamSource(new File(foo_xml)),}}
> {{ new StreamResult(System.out));}}
> {{ }}}
> {{}}}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18492) Enterprise Feature of Saxon is Disabled in Camel 3.x versions.
[
https://issues.apache.org/jira/browse/CAMEL-18492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602300#comment-17602300
]
Andrea Cosentino commented on CAMEL-18492:
--
As a side note even Michael Kay comments about this on Stack Overflow that this
feature is widely misunderstood
https://stackoverflow.com/questions/51378748/extension-functions-cannot-be-used-when-secure-feature-proccesing-is-set-to-true
> Enterprise Feature of Saxon is Disabled in Camel 3.x versions.
> --
>
> Key: CAMEL-18492
> URL: https://issues.apache.org/jira/browse/CAMEL-18492
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon, camel-xslt
>Affects Versions: 3.0.0
>Reporter: Harish Annamalai
>Priority: Major
>
> Hi All,
> We use Camel-Saxon for one of our product. We use Saxon Enterprise Edition
> 9.9.1.6.
> We are migrating our product from camel 2.x to camel 3.x (2.24 to 3.15 to be
> exact).
> We use a paid feature of Saxon; Invoking *External Java Functions* in XSL
> Transformations.
> We also *Extension Functions,* which we pass to camel-xslt-saxon component.
> What we have observed in camel 3.x versions and above, In class
> {{{*}XsltSaxonEndpoint{*}.java}} During the registration of extension
> functions, at line 202, {{registerSaxonExtensionFunctions}} method of
> {{{*}XsltSaxonHelper{*}.java}} is called.
>
> In XsltSaxonHelper.class, the method,
> {{{}registerSaxonExtensionFunctions{}}}, at line 55, sets a feature of
> {*}XMLConstants.FEATURE_SECURE_PROCESSING{*}.
> Unfortunately, Setting this Feature disables the External Java Function
> calls.
> We checked in Camel 2.x versions, this Feature is not set and therefore the
> External Java Calls work fine.
>
> We see this as a bug - The Feature *XMLConstants.FEATURE_SECURE_PROCESSING*
> is being introduced in 3.x and breaks a paid/Enterprise feature of Saxon.
>
> Sample Code to test:
> {{import javax.xml.XMLConstants;}}
> {{import javax.xml.transform.Transformer;}}
> {{import javax.xml.transform.TransformerException;}}
> {{import javax.xml.transform.TransformerFactory;}}
> {{import javax.xml.transform.stream.StreamResult;}}
> {{import javax.xml.transform.stream.StreamSource;}}
> {{import java.io.File;}}
> {{public class SaxonTransformationTester {}}
> {{ public static void main(String[] args) throws TransformerException {}}
> {{ String foo_xml = "src/main/resources/in.xml"; // input xml}}
> {{ String foo_xsl = "src/main/resources/transf.xml"; // input xsl}}
> {{ EnterpriseTransformerFactory eef =
> SaxonEEConsumerFactory.getEnterpriseTransformerFactoryInstance();}}
> {{
> eef.getConfiguration().getConfigurationProperty(Feature.ALLOW_EXTERNAL_FUNCTIONS);}}
> {{ eef.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true); //This
> causes External Functions to break}}
> {{
> eef.getConfiguration().setConfigurationProperty("http://saxon.sf.net/feature/trace-external-functions;,
> false);}}
> {{ Transformer transformer = eef.newTransformer(new StreamSource(}}
> {{ new File(foo_xsl)));}}
> {{ transformer.transform(new StreamSource(new File(foo_xml)),}}
> {{ new StreamResult(System.out));}}
> {{ }}}
> {{}}}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18492) Enterprise Feature of Saxon is Disabled in Camel 3.x versions.
[
https://issues.apache.org/jira/browse/CAMEL-18492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602297#comment-17602297
]
Andrea Cosentino edited comment on CAMEL-18492 at 9/9/22 12:08 PM:
---
It's a security best practice to the set FEATURE_SECURE_PROCESSING property to
true.
was (Author: ancosen):
It's a security best practice to the FEATURE_SECURE_PROCESSING to true.
> Enterprise Feature of Saxon is Disabled in Camel 3.x versions.
> --
>
> Key: CAMEL-18492
> URL: https://issues.apache.org/jira/browse/CAMEL-18492
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon, camel-xslt
>Affects Versions: 3.0.0
>Reporter: Harish Annamalai
>Priority: Major
>
> Hi All,
> We use Camel-Saxon for one of our product. We use Saxon Enterprise Edition
> 9.9.1.6.
> We are migrating our product from camel 2.x to camel 3.x (2.24 to 3.15 to be
> exact).
> We use a paid feature of Saxon; Invoking *External Java Functions* in XSL
> Transformations.
> We also *Extension Functions,* which we pass to camel-xslt-saxon component.
> What we have observed in camel 3.x versions and above, In class
> {{{*}XsltSaxonEndpoint{*}.java}} During the registration of extension
> functions, at line 202, {{registerSaxonExtensionFunctions}} method of
> {{{*}XsltSaxonHelper{*}.java}} is called.
>
> In XsltSaxonHelper.class, the method,
> {{{}registerSaxonExtensionFunctions{}}}, at line 55, sets a feature of
> {*}XMLConstants.FEATURE_SECURE_PROCESSING{*}.
> Unfortunately, Setting this Feature disables the External Java Function
> calls.
> We checked in Camel 2.x versions, this Feature is not set and therefore the
> External Java Calls work fine.
>
> We see this as a bug - The Feature *XMLConstants.FEATURE_SECURE_PROCESSING*
> is being introduced in 3.x and breaks a paid/Enterprise feature of Saxon.
>
> Sample Code to test:
> {{import javax.xml.XMLConstants;}}
> {{import javax.xml.transform.Transformer;}}
> {{import javax.xml.transform.TransformerException;}}
> {{import javax.xml.transform.TransformerFactory;}}
> {{import javax.xml.transform.stream.StreamResult;}}
> {{import javax.xml.transform.stream.StreamSource;}}
> {{import java.io.File;}}
> {{public class SaxonTransformationTester {}}
> {{ public static void main(String[] args) throws TransformerException {}}
> {{ String foo_xml = "src/main/resources/in.xml"; // input xml}}
> {{ String foo_xsl = "src/main/resources/transf.xml"; // input xsl}}
> {{ EnterpriseTransformerFactory eef =
> SaxonEEConsumerFactory.getEnterpriseTransformerFactoryInstance();}}
> {{
> eef.getConfiguration().getConfigurationProperty(Feature.ALLOW_EXTERNAL_FUNCTIONS);}}
> {{ eef.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true); //This
> causes External Functions to break}}
> {{
> eef.getConfiguration().setConfigurationProperty("http://saxon.sf.net/feature/trace-external-functions;,
> false);}}
> {{ Transformer transformer = eef.newTransformer(new StreamSource(}}
> {{ new File(foo_xsl)));}}
> {{ transformer.transform(new StreamSource(new File(foo_xml)),}}
> {{ new StreamResult(System.out));}}
> {{ }}}
> {{}}}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18492) Enterprise Feature of Saxon is Disabled in Camel 3.x versions.
[
https://issues.apache.org/jira/browse/CAMEL-18492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602297#comment-17602297
]
Andrea Cosentino commented on CAMEL-18492:
--
It's a security best practice to the FEATURE_SECURE_PROCESSING to true.
> Enterprise Feature of Saxon is Disabled in Camel 3.x versions.
> --
>
> Key: CAMEL-18492
> URL: https://issues.apache.org/jira/browse/CAMEL-18492
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon, camel-xslt
>Affects Versions: 3.0.0
>Reporter: Harish Annamalai
>Priority: Major
>
> Hi All,
> We use Camel-Saxon for one of our product. We use Saxon Enterprise Edition
> 9.9.1.6.
> We are migrating our product from camel 2.x to camel 3.x (2.24 to 3.15 to be
> exact).
> We use a paid feature of Saxon; Invoking *External Java Functions* in XSL
> Transformations.
> We also *Extension Functions,* which we pass to camel-xslt-saxon component.
> What we have observed in camel 3.x versions and above, In class
> {{{*}XsltSaxonEndpoint{*}.java}} During the registration of extension
> functions, at line 202, {{registerSaxonExtensionFunctions}} method of
> {{{*}XsltSaxonHelper{*}.java}} is called.
>
> In XsltSaxonHelper.class, the method,
> {{{}registerSaxonExtensionFunctions{}}}, at line 55, sets a feature of
> {*}XMLConstants.FEATURE_SECURE_PROCESSING{*}.
> Unfortunately, Setting this Feature disables the External Java Function
> calls.
> We checked in Camel 2.x versions, this Feature is not set and therefore the
> External Java Calls work fine.
>
> We see this as a bug - The Feature *XMLConstants.FEATURE_SECURE_PROCESSING*
> is being introduced in 3.x and breaks a paid/Enterprise feature of Saxon.
>
> Sample Code to test:
> {{import javax.xml.XMLConstants;}}
> {{import javax.xml.transform.Transformer;}}
> {{import javax.xml.transform.TransformerException;}}
> {{import javax.xml.transform.TransformerFactory;}}
> {{import javax.xml.transform.stream.StreamResult;}}
> {{import javax.xml.transform.stream.StreamSource;}}
> {{import java.io.File;}}
> {{public class SaxonTransformationTester {}}
> {{ public static void main(String[] args) throws TransformerException {}}
> {{ String foo_xml = "src/main/resources/in.xml"; // input xml}}
> {{ String foo_xsl = "src/main/resources/transf.xml"; // input xsl}}
> {{ EnterpriseTransformerFactory eef =
> SaxonEEConsumerFactory.getEnterpriseTransformerFactoryInstance();}}
> {{
> eef.getConfiguration().getConfigurationProperty(Feature.ALLOW_EXTERNAL_FUNCTIONS);}}
> {{ eef.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true); //This
> causes External Functions to break}}
> {{
> eef.getConfiguration().setConfigurationProperty("http://saxon.sf.net/feature/trace-external-functions;,
> false);}}
> {{ Transformer transformer = eef.newTransformer(new StreamSource(}}
> {{ new File(foo_xsl)));}}
> {{ transformer.transform(new StreamSource(new File(foo_xml)),}}
> {{ new StreamResult(System.out));}}
> {{ }}}
> {{}}}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (CAMEL-18454) Support Secrets Reload from Vault/Cloud Service through specific Tasks in components
[ https://issues.apache.org/jira/browse/CAMEL-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reopened CAMEL-18454: -- > Support Secrets Reload from Vault/Cloud Service through specific Tasks in > components > > > Key: CAMEL-18454 > URL: https://issues.apache.org/jira/browse/CAMEL-18454 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > We have some example of tasks for having a secret reload based on events in > the camel-examples repo. > We should try to do this for all the vault/cloud services we are supporting. > As far as I know Hashicorp Vault doesn't have a notification system for this > purpose, but I need to dig a bit. > List of components to support > - Camel-AWS-secrets-manager > - Camel-google-secrets-manager > - Camel-Azure-Key-vault > and maybe Camel-Hashicorp Vault -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18454) Support Secrets Reload from Vault/Cloud Service through specific Tasks in components
[ https://issues.apache.org/jira/browse/CAMEL-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18454. -- Resolution: Fixed > Support Secrets Reload from Vault/Cloud Service through specific Tasks in > components > > > Key: CAMEL-18454 > URL: https://issues.apache.org/jira/browse/CAMEL-18454 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > We have some example of tasks for having a secret reload based on events in > the camel-examples repo. > We should try to do this for all the vault/cloud services we are supporting. > As far as I know Hashicorp Vault doesn't have a notification system for this > purpose, but I need to dig a bit. > List of components to support > - Camel-AWS-secrets-manager > - Camel-google-secrets-manager > - Camel-Azure-Key-vault > and maybe Camel-Hashicorp Vault -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18487) Camel-AWS-Secrets-Manager: Cloudtrail task should support environment variables as configuration too
[ https://issues.apache.org/jira/browse/CAMEL-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18487. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Cloudtrail task should support environment > variables as configuration too > > > Key: CAMEL-18487 > URL: https://issues.apache.org/jira/browse/CAMEL-18487 > Project: Camel > Issue Type: Sub-task > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18487) Camel-AWS-Secrets-Manager: Cloudtrail task should support environment variables as configuration too
Andrea Cosentino created CAMEL-18487: Summary: Camel-AWS-Secrets-Manager: Cloudtrail task should support environment variables as configuration too Key: CAMEL-18487 URL: https://issues.apache.org/jira/browse/CAMEL-18487 Project: Camel Issue Type: Sub-task Components: camel-aws2 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18478) Support Secrets Reload from Vault/Cloud Service in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18478. -- Resolution: Fixed > Support Secrets Reload from Vault/Cloud Service in camel-spring-boot > - > > Key: CAMEL-18478 > URL: https://issues.apache.org/jira/browse/CAMEL-18478 > Project: Camel > Issue Type: Sub-task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18478) Support Secrets Reload from Vault/Cloud Service in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18478: - Summary: Support Secrets Reload from Vault/Cloud Service in camel-spring-boot (was: Support Secret Refresh in camel-spring-boot ) > Support Secrets Reload from Vault/Cloud Service in camel-spring-boot > - > > Key: CAMEL-18478 > URL: https://issues.apache.org/jira/browse/CAMEL-18478 > Project: Camel > Issue Type: Sub-task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18478) Support Secret Refresh in camel-spring-boot
Andrea Cosentino created CAMEL-18478: Summary: Support Secret Refresh in camel-spring-boot Key: CAMEL-18478 URL: https://issues.apache.org/jira/browse/CAMEL-18478 Project: Camel Issue Type: Sub-task Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18468) Camel-AWS-Secrets-Manager: Create a task looking for secrets update in CloudTrail
[ https://issues.apache.org/jira/browse/CAMEL-18468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18468. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Create a task looking for secrets update in > CloudTrail > - > > Key: CAMEL-18468 > URL: https://issues.apache.org/jira/browse/CAMEL-18468 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18468) Camel-AWS-Secrets-Manager: Create a task looking for secrets update in CloudTrail
[ https://issues.apache.org/jira/browse/CAMEL-18468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600597#comment-17600597 ] Andrea Cosentino commented on CAMEL-18468: -- [~davsclaus] it has been pushed, we could start from here to include the needed bits in the vault support. > Camel-AWS-Secrets-Manager: Create a task looking for secrets update in > CloudTrail > - > > Key: CAMEL-18468 > URL: https://issues.apache.org/jira/browse/CAMEL-18468 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18468) Camel-AWS-Secrets-Manager: Create a task looking for secrets update in CloudTrail
Andrea Cosentino created CAMEL-18468: Summary: Camel-AWS-Secrets-Manager: Create a task looking for secrets update in CloudTrail Key: CAMEL-18468 URL: https://issues.apache.org/jira/browse/CAMEL-18468 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18466) Camel-AWS2-SQS: Move from ComponentVerifierExtension to HealtCheck
Andrea Cosentino created CAMEL-18466: Summary: Camel-AWS2-SQS: Move from ComponentVerifierExtension to HealtCheck Key: CAMEL-18466 URL: https://issues.apache.org/jira/browse/CAMEL-18466 Project: Camel Issue Type: Improvement Components: camel-aws2 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18405) camel-karaf - Camel-file ResumeAware
[ https://issues.apache.org/jira/browse/CAMEL-18405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600228#comment-17600228 ] Andrea Cosentino commented on CAMEL-18405: -- It's resolved because the fix is in place. We don't wait for the release to come out for moving issues to resolved state. We resolve them before and we track the version containing the fix. > camel-karaf - Camel-file ResumeAware > > > Key: CAMEL-18405 > URL: https://issues.apache.org/jira/browse/CAMEL-18405 > Project: Camel > Issue Type: Bug >Affects Versions: 3.18.1 >Reporter: TARTIERE >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.18.2 > > > Unable to start application with routes listening for files. > java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: > org/apache/camel/resume/ResumeAware > at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?] > at java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?] > at > java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:199) > ~[?:?] > at > java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:230) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:195) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:447) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) > ~[?:?] > at > org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) > ~[?:?] > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817) > ~[?:?] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2336) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] > at > org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1160) > ~[?:?] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1041) > ~[?:?] > at >
[jira] [Resolved] (CAMEL-18405) camel-karaf - Camel-file ResumeAware
[ https://issues.apache.org/jira/browse/CAMEL-18405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18405. -- Resolution: Fixed > camel-karaf - Camel-file ResumeAware > > > Key: CAMEL-18405 > URL: https://issues.apache.org/jira/browse/CAMEL-18405 > Project: Camel > Issue Type: Bug >Affects Versions: 3.18.1 >Reporter: TARTIERE >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.18.2 > > > Unable to start application with routes listening for files. > java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: > org/apache/camel/resume/ResumeAware > at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?] > at java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?] > at > java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:199) > ~[?:?] > at > java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:230) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:195) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:447) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) > ~[?:?] > at > org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) > ~[?:?] > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817) > ~[?:?] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2336) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] > at > org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1160) > ~[?:?] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1041) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1069) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:1004) >
[jira] [Updated] (CAMEL-18462) LTS dates are not well documented in release notes
[ https://issues.apache.org/jira/browse/CAMEL-18462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18462: - Issue Type: Improvement (was: Bug) > LTS dates are not well documented in release notes > -- > > Key: CAMEL-18462 > URL: https://issues.apache.org/jira/browse/CAMEL-18462 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Sebb >Priority: Major > > The individual release pages for LTS releases (e.g. [1]) don't give a release > date or an EOL date. The release dates are mentioned on the release summary > page [2], however there is no link to this page from the individual release > pages. > It looks like the only documentation for the LTS dates is on the downloads > page [3], but that is not at all obvious, and does not cover recently > superseded releases. For example, what is the EOL for 3.8.0, released in July > 2022?. > It should be easier to find out this information from the releases notes. > For example they could be documented here [2], with backlinks from [1] etc. > [1] https://camel.apache.org/releases/release-3.14.5/ > [2] https://camel.apache.org/releases/ > [3] https://camel.apache.org/download/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18454) Support Secrets Reload from Vault/Cloud Service through specific Tasks in components
[ https://issues.apache.org/jira/browse/CAMEL-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18454: Assignee: Andrea Cosentino > Support Secrets Reload from Vault/Cloud Service through specific Tasks in > components > > > Key: CAMEL-18454 > URL: https://issues.apache.org/jira/browse/CAMEL-18454 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > > We have some example of tasks for having a secret reload based on events in > the camel-examples repo. > We should try to do this for all the vault/cloud services we are supporting. > As far as I know Hashicorp Vault doesn't have a notification system for this > purpose, but I need to dig a bit. > List of components to support > - Camel-AWS-secrets-manager > - Camel-google-secrets-manager > - Camel-Azure-Key-vault > and maybe Camel-Hashicorp Vault -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18454) Support Secrets Reload from Vault/Cloud Service through specific Tasks in components
[ https://issues.apache.org/jira/browse/CAMEL-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18454: - Description: We have some example of tasks for having a secret reload based on events in the camel-examples repo. We should try to do this for all the vault/cloud services we are supporting. As far as I know Hashicorp Vault doesn't have a notification system for this purpose, but I need to dig a bit. List of components to support - Camel-AWS-secrets-manager - Camel-google-secrets-manager - Camel-Azure-Key-vault and maybe Camel-Hashicorp Vault > Support Secrets Reload from Vault/Cloud Service through specific Tasks in > components > > > Key: CAMEL-18454 > URL: https://issues.apache.org/jira/browse/CAMEL-18454 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Priority: Major > > We have some example of tasks for having a secret reload based on events in > the camel-examples repo. > We should try to do this for all the vault/cloud services we are supporting. > As far as I know Hashicorp Vault doesn't have a notification system for this > purpose, but I need to dig a bit. > List of components to support > - Camel-AWS-secrets-manager > - Camel-google-secrets-manager > - Camel-Azure-Key-vault > and maybe Camel-Hashicorp Vault -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18454) Support Secrets Reload from Vault/Cloud Service through specific Tasks in components
Andrea Cosentino created CAMEL-18454: Summary: Support Secrets Reload from Vault/Cloud Service through specific Tasks in components Key: CAMEL-18454 URL: https://issues.apache.org/jira/browse/CAMEL-18454 Project: Camel Issue Type: Task Reporter: Andrea Cosentino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18444) camel-caffeine - Caffeine-cache query parameter action does not work
[
https://issues.apache.org/jira/browse/CAMEL-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598187#comment-17598187
]
Andrea Cosentino commented on CAMEL-18444:
--
In the example with the header it is working just because the endpoint it is
the same "caffeine-cache://cache?key=1", in that case the endpoint will be
re-used. In the case of invoking action the endpoint will be different between
first and second invocation, so you'll have a new "cache" cache and the GET
won't return any result.
> camel-caffeine - Caffeine-cache query parameter action does not work
>
>
> Key: CAMEL-18444
> URL: https://issues.apache.org/jira/browse/CAMEL-18444
> Project: Camel
> Issue Type: Bug
> Components: camel-caffeine
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Caffeine-cache example using headers works fine:
> {code:java}
> from("timer:test2")
> .setBody(constant("VALUE_1"))
> .setHeader("CamelCaffeineAction", constant("PUT"))
> .to("caffeine-cache://cache?key=1")
> .setBody(constant("VALUE_2"))
> .setHeader("CamelCaffeineAction", constant("GET"))
> .to("caffeine-cache://cache?key=1")
> .log("Result2: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
> Same code using query parameter action does not work:
> {code:java}
> from("timer:test1")
> .setBody(constant("VALUE_1"))
> .to("caffeine-cache://cache?action=PUT=1")
> .setBody(constant("VALUE_2"))
> .to("caffeine-cache://cache?key=1=GET")
> .log("Result1: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18444) camel-caffeine - Caffeine-cache query parameter action does not work
[
https://issues.apache.org/jira/browse/CAMEL-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598186#comment-17598186
]
Andrea Cosentino commented on CAMEL-18444:
--
You need to bind the cache "cache" to the registry, otherwise in the GET action
a cache named "cache" will be re-instantiated from scratch.
> camel-caffeine - Caffeine-cache query parameter action does not work
>
>
> Key: CAMEL-18444
> URL: https://issues.apache.org/jira/browse/CAMEL-18444
> Project: Camel
> Issue Type: Bug
> Components: camel-caffeine
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Caffeine-cache example using headers works fine:
> {code:java}
> from("timer:test2")
> .setBody(constant("VALUE_1"))
> .setHeader("CamelCaffeineAction", constant("PUT"))
> .to("caffeine-cache://cache?key=1")
> .setBody(constant("VALUE_2"))
> .setHeader("CamelCaffeineAction", constant("GET"))
> .to("caffeine-cache://cache?key=1")
> .log("Result2: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
> Same code using query parameter action does not work:
> {code:java}
> from("timer:test1")
> .setBody(constant("VALUE_1"))
> .to("caffeine-cache://cache?action=PUT=1")
> .setBody(constant("VALUE_2"))
> .to("caffeine-cache://cache?key=1=GET")
> .log("Result1: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (CAMEL-17135) camel-debezium-mongodb-starter does not pupulate values from application.properties
[
https://issues.apache.org/jira/browse/CAMEL-17135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reopened CAMEL-17135:
--
> camel-debezium-mongodb-starter does not pupulate values from
> application.properties
> ---
>
> Key: CAMEL-17135
> URL: https://issues.apache.org/jira/browse/CAMEL-17135
> Project: Camel
> Issue Type: Bug
> Components: camel-debezium
>Affects Versions: 3.11.3
> Environment: Ubuntu 20.04
> jdk 11
>Reporter: Andrii Melashchenko
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.13.0, 3.11.4
>
>
> When trying to build simple route
> from({color:#6a8759}"debezium-mongodb:meteor"{color})
> with spring-boot properties
> ```
> {color:#cc7832}camel.component.debezium-mongodb.mongodb-hosts{color}{color:#808080}={color}{color:#6a8759}localhost:3001
> {color}{color:#cc7832}camel.component.debezium-mongodb.mongodb-user{color}{color:#808080}={color}{color:#6a8759}test
> {color}{color:#cc7832}camel.component.debezium-mongodb.mongodb-password{color}{color:#808080}={color}{color:#6a8759}test
> {color}{color:#cc7832}camel.component.debezium-mongodb.mongodb-name{color}{color:#808080}={color}{color:#6a8759}test
> {color}{color:#cc7832}camel.component.debezium-mongodb.offset-storage-file-filename{color}{color:#808080}={color}{color:#6a8759}/tmp/offset-file-1.dat
> {color}{color:#cc7832}camel.component.debezium-mongodb.database-history-file-filename{color}{color:#808080}={color}{color:#6a8759}/tmp/history-file-1.dat
> {color}
> ```
> Route fails with error
> ```
> Required field 'offsetStorageFileName' must be set since 'offsetStorage' is
> set to
> ```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18427) Camel Debezium with Postgres on Spring Boot doesn't work
[
https://issues.apache.org/jira/browse/CAMEL-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-18427:
-
Summary: Camel Debezium with Postgres on Spring Boot doesn't work (was:
Camel Debezium with Postgres)
> Camel Debezium with Postgres on Spring Boot doesn't work
>
>
> Key: CAMEL-18427
> URL: https://issues.apache.org/jira/browse/CAMEL-18427
> Project: Camel
> Issue Type: Bug
> Components: camel-debezium
>Affects Versions: 3.13.0
> Environment: Jdk 17
> Windows 10
> Spring boot
>Reporter: michael elbaz
>Priority: Major
> Attachments: image-2022-08-24-12-12-27-542.png,
> image-2022-08-24-12-19-55-853.png
>
>
> From camel 3.13.0 Camel Debezium simply not working is work perfectly with
> camel older than 3.13.0
> here the code
> {code:java}
> @Override
> public void configure() throws Exception {
> String DATABASE_READER = "debezium-postgres:localhost?"
> + "databaseHostname=localhost"
> + "=5432"
> + "=postgres"
> + "=test"
> + "=test"
> + "=localhost"
> + "=public"
> + "=public.*"
> + "=/tmp/offset-file-1.dat"
> + "=1"
> + "=pgoutput";
> from(DATABASE_READER)
> .routeId("debeziumPGRoute")
> .log("Response : ${body}");
> }
> {code}
> !image-2022-08-24-12-12-27-542.png|width=949,height=240!
> I check this [changelog|https://camel.apache.org/releases/release-3.13.0/]
> !image-2022-08-24-12-19-55-853.png|width=803,height=402!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18422) Camel-AWS Component: Explicitly add AWS SDK Utils dependency
[ https://issues.apache.org/jira/browse/CAMEL-18422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18422. -- Resolution: Won't Fix Superseded by CAMEL-18424 > Camel-AWS Component: Explicitly add AWS SDK Utils dependency > - > > Key: CAMEL-18422 > URL: https://issues.apache.org/jira/browse/CAMEL-18422 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.2, 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (CAMEL-18422) Camel-AWS Component: Explicitly add AWS SDK Utils dependency
[ https://issues.apache.org/jira/browse/CAMEL-18422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reopened CAMEL-18422: -- > Camel-AWS Component: Explicitly add AWS SDK Utils dependency > - > > Key: CAMEL-18422 > URL: https://issues.apache.org/jira/browse/CAMEL-18422 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.2, 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18422) Camel-AWS Component: Explicitly add AWS SDK Utils dependency
[ https://issues.apache.org/jira/browse/CAMEL-18422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18422: - Fix Version/s: 3.18.2 > Camel-AWS Component: Explicitly add AWS SDK Utils dependency > - > > Key: CAMEL-18422 > URL: https://issues.apache.org/jira/browse/CAMEL-18422 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.2, 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18422) Camel-AWS Component: Explicitly add AWS SDK Utils dependency
[ https://issues.apache.org/jira/browse/CAMEL-18422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18422. -- Resolution: Fixed > Camel-AWS Component: Explicitly add AWS SDK Utils dependency > - > > Key: CAMEL-18422 > URL: https://issues.apache.org/jira/browse/CAMEL-18422 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18422) Camel-AWS Component: Explicitly add AWS SDK Utils dependency
Andrea Cosentino created CAMEL-18422: Summary: Camel-AWS Component: Explicitly add AWS SDK Utils dependency Key: CAMEL-18422 URL: https://issues.apache.org/jira/browse/CAMEL-18422 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18354) Camel AWS Cloudtrail: Create Karaf feature
[ https://issues.apache.org/jira/browse/CAMEL-18354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18354. -- Resolution: Fixed > Camel AWS Cloudtrail: Create Karaf feature > -- > > Key: CAMEL-18354 > URL: https://issues.apache.org/jira/browse/CAMEL-18354 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18354) Camel AWS Cloudtrail: Create Karaf feature
Andrea Cosentino created CAMEL-18354: Summary: Camel AWS Cloudtrail: Create Karaf feature Key: CAMEL-18354 URL: https://issues.apache.org/jira/browse/CAMEL-18354 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18301) Component for Sharepoint Lists (Office 365)
[ https://issues.apache.org/jira/browse/CAMEL-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575369#comment-17575369 ] Andrea Cosentino commented on CAMEL-18301: -- So this would require an http component dealing with their REST Api. > Component for Sharepoint Lists (Office 365) > --- > > Key: CAMEL-18301 > URL: https://issues.apache.org/jira/browse/CAMEL-18301 > Project: Camel > Issue Type: New Feature >Reporter: Adrien SALES >Priority: Minor > Labels: features > > h1. Context > > more and more users store data in Sharepoint LIsts on sharepointOnline. The > tricky part comes when we are asked to perform integrations with these DATAs. > They are served as REST APIs, OIDC and oAUth options are available but you be > awesome to be able to grab these datas as easily as we can with the JDBC > component for example. > > Our main usecase by the way is to copy data from SharepointLists to JDBC data > sources... or Kafka topics. > > h1. Feature request > > * Add the Microsoft Sharepoint List component to core components > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18301) Component for Sharepoint Lists (Office 365)
[ https://issues.apache.org/jira/browse/CAMEL-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575368#comment-17575368 ] Andrea Cosentino commented on CAMEL-18301: -- As far as I see there is not an sdk to deal with Sharepoint. > Component for Sharepoint Lists (Office 365) > --- > > Key: CAMEL-18301 > URL: https://issues.apache.org/jira/browse/CAMEL-18301 > Project: Camel > Issue Type: New Feature >Reporter: Adrien SALES >Priority: Minor > Labels: features > > h1. Context > > more and more users store data in Sharepoint LIsts on sharepointOnline. The > tricky part comes when we are asked to perform integrations with these DATAs. > They are served as REST APIs, OIDC and oAUth options are available but you be > awesome to be able to grab these datas as easily as we can with the JDBC > component for example. > > Our main usecase by the way is to copy data from SharepointLists to JDBC data > sources... or Kafka topics. > > h1. Feature request > > * Add the Microsoft Sharepoint List component to core components > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18352) Camel-AWS Cloudtrail: Create an SB starter
[ https://issues.apache.org/jira/browse/CAMEL-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18352. -- Resolution: Fixed > Camel-AWS Cloudtrail: Create an SB starter > -- > > Key: CAMEL-18352 > URL: https://issues.apache.org/jira/browse/CAMEL-18352 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18352) Camel-AWS Cloudtrail: Create an SB starter
[ https://issues.apache.org/jira/browse/CAMEL-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18352: - Summary: Camel-AWS Cloudtrail: Create an SB starter (was: Camel-AWS Cloud trail: Create an SB starter) > Camel-AWS Cloudtrail: Create an SB starter > -- > > Key: CAMEL-18352 > URL: https://issues.apache.org/jira/browse/CAMEL-18352 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18352) Camel-AWS Cloud trail: Create an SB starter
Andrea Cosentino created CAMEL-18352: Summary: Camel-AWS Cloud trail: Create an SB starter Key: CAMEL-18352 URL: https://issues.apache.org/jira/browse/CAMEL-18352 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18340) implement camel-sapjcoserver component
[ https://issues.apache.org/jira/browse/CAMEL-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18340. -- Resolution: Won't Fix > implement camel-sapjcoserver component > --- > > Key: CAMEL-18340 > URL: https://issues.apache.org/jira/browse/CAMEL-18340 > Project: Camel > Issue Type: New Feature >Reporter: WangYan >Priority: Minor > > Hello Camel Riders > I am using many integrations between SAP ABAP <->Camel/JAVA during my daily > work > Therefore I want to implement camel-sapjcoserver component (consumer only) > which can recieve SAP ABAP calls result and wrap it as exchange for next step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18340) implement camel-sapjcoserver component
[ https://issues.apache.org/jira/browse/CAMEL-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574577#comment-17574577 ] Andrea Cosentino commented on CAMEL-18340: -- It's not possible to add a component based on SAP libraries, they are not compatible with ASF license. The examples are different because we are not releasing them, so we could eventually add a provided dependency, but for released artifacts we cannot do it. So this cannot be done or assigned. If you want to work on 3rd party component with particular licenses you need to look at camel-extras https://github.com/camel-extra/camel-extra > implement camel-sapjcoserver component > --- > > Key: CAMEL-18340 > URL: https://issues.apache.org/jira/browse/CAMEL-18340 > Project: Camel > Issue Type: New Feature >Reporter: WangYan >Priority: Minor > > Hello Camel Riders > I am using many integrations between SAP ABAP <->Camel/JAVA during my daily > work > Therefore I want to implement camel-sapjcoserver component (consumer only) > which can recieve SAP ABAP calls result and wrap it as exchange for next step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18326) google-mail-stream
[
https://issues.apache.org/jira/browse/CAMEL-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573052#comment-17573052
]
Andrea Cosentino commented on CAMEL-18326:
--
I think you could use any dataformat immediately after consuming and transform
the body in the format you want to display or consume. There is no advantages
in adding an option to choose the output, because what you would do in the
component, it is what the dataformat would do immediately after consuming the
message.
> google-mail-stream
> --
>
> Key: CAMEL-18326
> URL: https://issues.apache.org/jira/browse/CAMEL-18326
> Project: Camel
> Issue Type: Improvement
> Components: camel-google-mail-stream
>Affects Versions: 3.16.0
>Reporter: Jérôme GARCIA
>Priority: Minor
> Labels: camel-core, google
>
> Hello,
>
> In *google-mail-stream* component, the mail body is displayed as plain text
> and is not easy to manipulate the data.
> The component should add the possibility to change this behavior and
> displayed a standardize object (JSON or other).
>
> {code:java}
> // code placeholder
> from('google-mail-stream:index?' +
> 'applicationName={{camel-app-name}}&' +
> 'accessToken={{gmail.client.access.token}}&' +
> 'refreshToken={{gmail.client.access.refresh.token}}&' +
> 'clientId={{gmail.client.id}}&' +
> 'query=is:unread&' +
> 'clientSecret={{gmail.client.secret}}')
> .log('${body}') {code}
>
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-15566) Create a AWS Cloudtrail component
[ https://issues.apache.org/jira/browse/CAMEL-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-15566. -- Resolution: Fixed > Create a AWS Cloudtrail component > - > > Key: CAMEL-15566 > URL: https://issues.apache.org/jira/browse/CAMEL-15566 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-15566) Create a AWS Cloudtrail component
[ https://issues.apache.org/jira/browse/CAMEL-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572976#comment-17572976 ] Andrea Cosentino commented on CAMEL-15566: -- Initial implementation pushed. > Create a AWS Cloudtrail component > - > > Key: CAMEL-15566 > URL: https://issues.apache.org/jira/browse/CAMEL-15566 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18313) Trait owner.target-annotations is not propagated to K8S Services
[
https://issues.apache.org/jira/browse/CAMEL-18313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-18313.
--
Resolution: Invalid
Open the issue in camel-k github repository in the issues section. Thanks.
> Trait owner.target-annotations is not propagated to K8S Services
>
>
> Key: CAMEL-18313
> URL: https://issues.apache.org/jira/browse/CAMEL-18313
> Project: Camel
> Issue Type: Bug
> Components: camel-k
>Reporter: Ruben Romero Montes
>Priority: Major
>
> When using the Owner Trait to propagate annotations to the owned resources,
> such annotations are not propagated to the Kubernetes Services.
>
> {code:java}
> # camel-k: language=yaml
> # camel-k: trait=owner.enabled=true
> # camel-k: trait=owner.target-annotations=[example]{code}
>
> The deployment shows the annotation but the service doesn't.
> Is this the expected behaviour?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create
[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reopened CAMEL-16287: -- It's not totally clear because looking at the https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_ListQueues.html the maxResults is not mandatory. > camel-aws2-sqs should use pagination for deciding which aws sqs queues it > should create > --- > > Key: CAMEL-16287 > URL: https://issues.apache.org/jira/browse/CAMEL-16287 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.3, 3.8.0 >Reporter: Gyorgy Abraham >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.14.4, 3.18.0 > > > There is an auto create queue feature for aws-sqs in camel-sqs component. > Upon camel context creation / route building, it issues an API call to list > all sqs queues, so it skips the creation for already existing ones. If camel > context has a for example consumer route for an sqs queue that is not listed > in the response of this API call, camel will try to to create it. > However, this API only lists the first 1000 queues in the current account. If > there are more then 1000 queues, camel-sqs will try to create a new one, and > might fail. In our company's account, we have 1442 queues in our account and > Camel tried to create a .fifo queue because it thought it wasnt already > existing, resulting in application startup error. > Relevant code: > [https://github.com/apache/camel/blob/master/components/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Endpoint.java#L174] > Relevant API docs at AWS: > [https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/sqs/AmazonSQS.html#listQueues-com.amazonaws.services.sqs.model.ListQueuesRequest-] > Solution is straightforward: use pagination and load all queues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-15566) Create a AWS Cloudtrail component
[ https://issues.apache.org/jira/browse/CAMEL-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-15566: - Fix Version/s: 3.19.0 (was: 3.x) > Create a AWS Cloudtrail component > - > > Key: CAMEL-15566 > URL: https://issues.apache.org/jira/browse/CAMEL-15566 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-15965) Create a Azure Functions component
[ https://issues.apache.org/jira/browse/CAMEL-15965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-15965. -- Resolution: Won't Fix There is no Java SDK for this purpose, but we could use any http component. > Create a Azure Functions component > -- > > Key: CAMEL-15965 > URL: https://issues.apache.org/jira/browse/CAMEL-15965 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17841) camel-azure - Add checkpoint events by batch
[ https://issues.apache.org/jira/browse/CAMEL-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17841. -- Resolution: Fixed > camel-azure - Add checkpoint events by batch > > > Key: CAMEL-17841 > URL: https://issues.apache.org/jira/browse/CAMEL-17841 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Kévin LACIRE >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.19.0 > > > Currently the Azure Eventhub consumer is checkpoint it's offset on [every > processed > exchange|https://github.com/apache/camel/blob/cb9d18559c2a482445be47ff28d423e1ddcdb7e9/components/camel-azure/camel-azure-eventhubs/src/main/java/org/apache/camel/component/azure/eventhubs/EventHubsConsumer.java#L149] > a quick upgrade would be to expose a *batchSize* parameter to execute this > checkpoint less frequently (this dramatically alter consumption performances) > a time interval could also be complementary to avoid potentially unlimited > pending checkpoint of the last batch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-17841) camel-azure - Add checkpoint events by batch
[ https://issues.apache.org/jira/browse/CAMEL-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-17841: Assignee: Andrea Cosentino > camel-azure - Add checkpoint events by batch > > > Key: CAMEL-17841 > URL: https://issues.apache.org/jira/browse/CAMEL-17841 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Kévin LACIRE >Assignee: Andrea Cosentino >Priority: Minor > > Currently the Azure Eventhub consumer is checkpoint it's offset on [every > processed > exchange|https://github.com/apache/camel/blob/cb9d18559c2a482445be47ff28d423e1ddcdb7e9/components/camel-azure/camel-azure-eventhubs/src/main/java/org/apache/camel/component/azure/eventhubs/EventHubsConsumer.java#L149] > a quick upgrade would be to expose a *batchSize* parameter to execute this > checkpoint less frequently (this dramatically alter consumption performances) > a time interval could also be complementary to avoid potentially unlimited > pending checkpoint of the last batch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-17841) camel-azure - Add checkpoint events by batch
[ https://issues.apache.org/jira/browse/CAMEL-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17841: - Fix Version/s: 3.19.0 > camel-azure - Add checkpoint events by batch > > > Key: CAMEL-17841 > URL: https://issues.apache.org/jira/browse/CAMEL-17841 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Kévin LACIRE >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.19.0 > > > Currently the Azure Eventhub consumer is checkpoint it's offset on [every > processed > exchange|https://github.com/apache/camel/blob/cb9d18559c2a482445be47ff28d423e1ddcdb7e9/components/camel-azure/camel-azure-eventhubs/src/main/java/org/apache/camel/component/azure/eventhubs/EventHubsConsumer.java#L149] > a quick upgrade would be to expose a *batchSize* parameter to execute this > checkpoint less frequently (this dramatically alter consumption performances) > a time interval could also be complementary to avoid potentially unlimited > pending checkpoint of the last batch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18287) Camel-AWS Eventbridge: Support operation putEvents to send custom event to Eventbridge
[ https://issues.apache.org/jira/browse/CAMEL-18287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18287. -- Resolution: Fixed > Camel-AWS Eventbridge: Support operation putEvents to send custom event to > Eventbridge > -- > > Key: CAMEL-18287 > URL: https://issues.apache.org/jira/browse/CAMEL-18287 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18287) Camel-AWS Eventbridge: Support operation putEvents to send custom event to Eventbridge
Andrea Cosentino created CAMEL-18287: Summary: Camel-AWS Eventbridge: Support operation putEvents to send custom event to Eventbridge Key: CAMEL-18287 URL: https://issues.apache.org/jira/browse/CAMEL-18287 Project: Camel Issue Type: New Feature Components: camel-aws2 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-18273) [Camel Spring Boot Examples] Add Saga EIP example
[ https://issues.apache.org/jira/browse/CAMEL-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18273 started by Andrea Cosentino. > [Camel Spring Boot Examples] Add Saga EIP example > - > > Key: CAMEL-18273 > URL: https://issues.apache.org/jira/browse/CAMEL-18273 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > Implement a new Camel Spring Boot example, to show how the > [Saga|https://camel.apache.org/components/latest/eips/saga-eip.html] works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18273) [Camel Spring Boot Examples] Add Saga EIP example
[ https://issues.apache.org/jira/browse/CAMEL-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18273: Assignee: Andrea Cosentino > [Camel Spring Boot Examples] Add Saga EIP example > - > > Key: CAMEL-18273 > URL: https://issues.apache.org/jira/browse/CAMEL-18273 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > Implement a new Camel Spring Boot example, to show how the > [Saga|https://camel.apache.org/components/latest/eips/saga-eip.html] works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18273) [Camel Spring Boot Examples] Add Saga EIP example
[ https://issues.apache.org/jira/browse/CAMEL-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18273. -- Resolution: Fixed > [Camel Spring Boot Examples] Add Saga EIP example > - > > Key: CAMEL-18273 > URL: https://issues.apache.org/jira/browse/CAMEL-18273 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > Implement a new Camel Spring Boot example, to show how the > [Saga|https://camel.apache.org/components/latest/eips/saga-eip.html] works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18273) [Camel Spring Boot Examples] Add Saga EIP example
[ https://issues.apache.org/jira/browse/CAMEL-18273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18273: - Fix Version/s: 3.19.0 > [Camel Spring Boot Examples] Add Saga EIP example > - > > Key: CAMEL-18273 > URL: https://issues.apache.org/jira/browse/CAMEL-18273 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Marco Carletti >Priority: Major > Fix For: 3.19.0 > > > Implement a new Camel Spring Boot example, to show how the > [Saga|https://camel.apache.org/components/latest/eips/saga-eip.html] works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18269) [Camel Spring Boot Examples] Update version
[ https://issues.apache.org/jira/browse/CAMEL-18269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18269: - Fix Version/s: 3.19.0 > [Camel Spring Boot Examples] Update version > > > Key: CAMEL-18269 > URL: https://issues.apache.org/jira/browse/CAMEL-18269 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Marco Carletti >Priority: Major > Fix For: 3.19.0 > > > Since the version of Camel Spring Boot has been released > [camel-spring-boot-3.18.0|https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.18.0] > the version of the > [examples|https://github.com/apache/camel-spring-boot-examples] should be > updated as well, increasing the snapshot and creating the tag -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18269) [Camel Spring Boot Examples] Update version
[ https://issues.apache.org/jira/browse/CAMEL-18269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18269. -- Resolution: Fixed > [Camel Spring Boot Examples] Update version > > > Key: CAMEL-18269 > URL: https://issues.apache.org/jira/browse/CAMEL-18269 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > Since the version of Camel Spring Boot has been released > [camel-spring-boot-3.18.0|https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.18.0] > the version of the > [examples|https://github.com/apache/camel-spring-boot-examples] should be > updated as well, increasing the snapshot and creating the tag -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18269) [Camel Spring Boot Examples] Update version
[ https://issues.apache.org/jira/browse/CAMEL-18269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18269: Assignee: Andrea Cosentino > [Camel Spring Boot Examples] Update version > > > Key: CAMEL-18269 > URL: https://issues.apache.org/jira/browse/CAMEL-18269 > Project: Camel > Issue Type: Task > Components: examples >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > Since the version of Camel Spring Boot has been released > [camel-spring-boot-3.18.0|https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.18.0] > the version of the > [examples|https://github.com/apache/camel-spring-boot-examples] should be > updated as well, increasing the snapshot and creating the tag -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18272) Camel-AWS2-Lambda: Support Function URL management through producer operations
Andrea Cosentino created CAMEL-18272: Summary: Camel-AWS2-Lambda: Support Function URL management through producer operations Key: CAMEL-18272 URL: https://issues.apache.org/jira/browse/CAMEL-18272 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18156) Add support for hyperledger-aries
[ https://issues.apache.org/jira/browse/CAMEL-18156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18156. -- Resolution: Fixed > Add support for hyperledger-aries > - > > Key: CAMEL-18156 > URL: https://issues.apache.org/jira/browse/CAMEL-18156 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.19.0 > > > With Nessus Aries we explore aspects of digital identy and verifiable > credentials based on Hyperledger Aries. > Who is going to control our digitial identity? Digital forms of our birth > certificate, passport, drivers license, medical records, vaccination > certificates, univeristy degrees, property certificates, etc. Is it the > state, a corporation or should we be in control ourselves? > https://github.com/tdiesler/nessus-aries -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18156) Add support for hyperledger-aries
[ https://issues.apache.org/jira/browse/CAMEL-18156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18156: - Fix Version/s: 3.19.0 > Add support for hyperledger-aries > - > > Key: CAMEL-18156 > URL: https://issues.apache.org/jira/browse/CAMEL-18156 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.19.0 > > > With Nessus Aries we explore aspects of digital identy and verifiable > credentials based on Hyperledger Aries. > Who is going to control our digitial identity? Digital forms of our birth > certificate, passport, drivers license, medical records, vaccination > certificates, univeristy degrees, property certificates, etc. Is it the > state, a corporation or should we be in control ourselves? > https://github.com/tdiesler/nessus-aries -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
[
https://issues.apache.org/jira/browse/CAMEL-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-18208:
-
Fix Version/s: 3.19.0
> vault: allow to retrieve a specific secret version/revision
> ---
>
> Key: CAMEL-18208
> URL: https://issues.apache.org/jira/browse/CAMEL-18208
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.19.0
>
>
> The vaults for which we have support in Apache Camel support versioned
> secrets (i.e. [1][2]) and it would be very useful to have an option to
> include the verison/revision of the secret in the vault property syntax, as
> example:
> {{aws:username@123}}
> This would mean to get the secret named username and version 123 from the
> aws vault.
> [1]
> https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
> [2]
> https://learn.hashicorp.com/tutorials/vault/versioned-kv#step-7-configure-automatic-data-deletion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
[
https://issues.apache.org/jira/browse/CAMEL-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-18208.
--
Resolution: Fixed
> vault: allow to retrieve a specific secret version/revision
> ---
>
> Key: CAMEL-18208
> URL: https://issues.apache.org/jira/browse/CAMEL-18208
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.19.0
>
>
> The vaults for which we have support in Apache Camel support versioned
> secrets (i.e. [1][2]) and it would be very useful to have an option to
> include the verison/revision of the secret in the vault property syntax, as
> example:
> {{aws:username@123}}
> This would mean to get the secret named username and version 123 from the
> aws vault.
> [1]
> https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
> [2]
> https://learn.hashicorp.com/tutorials/vault/versioned-kv#step-7-configure-automatic-data-deletion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-17688) Support ability to load properties from Vault/Secrets cloud services - Hashicorp Vault
[ https://issues.apache.org/jira/browse/CAMEL-17688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17688. -- Resolution: Fixed > Support ability to load properties from Vault/Secrets cloud services - > Hashicorp Vault > -- > > Key: CAMEL-17688 > URL: https://issues.apache.org/jira/browse/CAMEL-17688 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > We need an Hashicorp Vault component, based on spring vault library. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18270) IMAP skipFailedMessage=true, but route blocked if mail is moved while download
[
https://issues.apache.org/jira/browse/CAMEL-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-18270:
-
Priority: Major (was: Critical)
> IMAP skipFailedMessage=true, but route blocked if mail is moved while download
> --
>
> Key: CAMEL-18270
> URL: https://issues.apache.org/jira/browse/CAMEL-18270
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Priority: Major
>
>
> Our imap mail route on the production system gets blocked when someone or an
> other systems moves / deletes an email from the inbox, while the camel mail
> route is loading the mail. As we do not have full control on the mailboxes we
> enabled skipFailedMessage but the issue remains.
> The following exception is written is the log, but the mail consumer is
> blocked. The issue can only be resolved by a restart of the service.
> {code:java}
> 2022-07-14 09:17:28.714 WARN 5465 --- [fice365.com:993]
> o.a.c.i.engine.DefaultReactiveExecutor : Error executing reactive work due
> to Error accessing headers due to: Cannot load header. This exception is
> ignored.
> org.apache.camel.RuntimeCamelException: Error accessing headers due to:
> Cannot load header
> at
> org.apache.camel.component.mail.MailMessage.populateInitialHeaders(MailMessage.java:107)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.DefaultMessage.createHeaders(DefaultMessage.java:331)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.DefaultMessage.hasHeaders(DefaultMessage.java:305)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.AbstractExchange.copy(AbstractExchange.java:140)
> ~[camel-support-3.18.0.jar:3.18.0]
> at org.apache.camel.support.DefaultExchange.copy(DefaultExchange.java:27)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ExchangeHelper.createCopy(ExchangeHelper.java:322)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.defensiveCopyExchangeIfNeeded(RedeliveryErrorHandler.java:304)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.prepare(RedeliveryErrorHandler.java:680)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.PrototypeTaskFactory.acquire(PrototypeTaskFactory.java:29)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:210)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:109)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:189)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:61)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:184)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:41)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.processExchange(MailConsumer.java:451)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.processBatch(MailConsumer.java:260)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:165)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> ~[na:na]
> at
> java.base/java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:305)
> ~[na:na]
> at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java)
[jira] [Reopened] (CAMEL-17688) Support ability to load properties from Vault/Secrets cloud services - Hashicorp Vault
[ https://issues.apache.org/jira/browse/CAMEL-17688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reopened CAMEL-17688: -- > Support ability to load properties from Vault/Secrets cloud services - > Hashicorp Vault > -- > > Key: CAMEL-17688 > URL: https://issues.apache.org/jira/browse/CAMEL-17688 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > We need an Hashicorp Vault component, based on spring vault library. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17689) Create a Camel Hashicorp Vault Component
[ https://issues.apache.org/jira/browse/CAMEL-17689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17689. -- Resolution: Fixed > Create a Camel Hashicorp Vault Component > > > Key: CAMEL-17689 > URL: https://issues.apache.org/jira/browse/CAMEL-17689 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > > https://github.com/spring-projects/spring-vault -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-17689) Create a Camel Hashicorp Vault Component
[ https://issues.apache.org/jira/browse/CAMEL-17689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17689: - Fix Version/s: 3.18.0 (was: 3.19.0) > Create a Camel Hashicorp Vault Component > > > Key: CAMEL-17689 > URL: https://issues.apache.org/jira/browse/CAMEL-17689 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > > https://github.com/spring-projects/spring-vault -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
[
https://issues.apache.org/jira/browse/CAMEL-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565101#comment-17565101
]
Andrea Cosentino edited comment on CAMEL-18208 at 7/13/22 12:47 PM:
AWS Secret Manager - DONE
Google Secrets Manager - DONE
Azure Key Vault - DONE
was (Author: ancosen):
AWS Secret Manager - DONE
Google Secrets Manager - DONE
> vault: allow to retrieve a specific secret version/revision
> ---
>
> Key: CAMEL-18208
> URL: https://issues.apache.org/jira/browse/CAMEL-18208
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Minor
>
> The vaults for which we have support in Apache Camel support versioned
> secrets (i.e. [1][2]) and it would be very useful to have an option to
> include the verison/revision of the secret in the vault property syntax, as
> example:
> {{aws:username@123}}
> This would mean to get the secret named username and version 123 from the
> aws vault.
> [1]
> https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
> [2]
> https://learn.hashicorp.com/tutorials/vault/versioned-kv#step-7-configure-automatic-data-deletion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18257) Camel-Hashicorp-vault: Support list secrets operation
[ https://issues.apache.org/jira/browse/CAMEL-18257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18257. -- Resolution: Fixed > Camel-Hashicorp-vault: Support list secrets operation > - > > Key: CAMEL-18257 > URL: https://issues.apache.org/jira/browse/CAMEL-18257 > Project: Camel > Issue Type: New Feature > Components: camel-hashicorp-vault >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18257) Camel-Hashicorp-vault: Support list secrets operation
[ https://issues.apache.org/jira/browse/CAMEL-18257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18257: - Fix Version/s: 3.18.0 (was: 3.19.0) > Camel-Hashicorp-vault: Support list secrets operation > - > > Key: CAMEL-18257 > URL: https://issues.apache.org/jira/browse/CAMEL-18257 > Project: Camel > Issue Type: New Feature > Components: camel-hashicorp-vault >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18268) Camel-dependencies is misaligned to current version in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18268. -- Resolution: Fixed > Camel-dependencies is misaligned to current version in camel-spring-boot > > > Key: CAMEL-18268 > URL: https://issues.apache.org/jira/browse/CAMEL-18268 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > > The camel-dependencies version is 3.18.0-SNAPSHOT in > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L26 and the > current version is 3.19.0-SNAPSHOT > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18268) Camel-dependencies is misaligned to current version in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18268: - Affects Version/s: (was: 3.19.0) > Camel-dependencies is misaligned to current version in camel-spring-boot > > > Key: CAMEL-18268 > URL: https://issues.apache.org/jira/browse/CAMEL-18268 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > > The camel-dependencies version is 3.18.0-SNAPSHOT in > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L26 and the > current version is 3.19.0-SNAPSHOT > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18268) Camel-dependencies is misaligned to current version in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18268: Assignee: Andrea Cosentino > Camel-dependencies is misaligned to current version in camel-spring-boot > > > Key: CAMEL-18268 > URL: https://issues.apache.org/jira/browse/CAMEL-18268 > Project: Camel > Issue Type: Bug > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Marco Carletti >Assignee: Andrea Cosentino >Priority: Major > > The camel-dependencies version is 3.18.0-SNAPSHOT in > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L26 and the > current version is 3.19.0-SNAPSHOT > https://github.com/apache/camel-spring-boot/blob/main/pom.xml#L31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565937#comment-17565937 ] Andrea Cosentino commented on CAMEL-18267: -- cc [~davsclaus] [~lburgazzoli] > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.x > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18267: - Description: In case of rotation, update, patch etc. We need to trigger a reload. This might be a service running with the properties source or something we could enable on-demand. In this way we could react to events. was:cc [~davsclaus] > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.x > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
Andrea Cosentino created CAMEL-18267: Summary: Vault Support: Trigger a reload of properties from a particular Vault source based on events Key: CAMEL-18267 URL: https://issues.apache.org/jira/browse/CAMEL-18267 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Fix For: 3.x cc [~davsclaus] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
[
https://issues.apache.org/jira/browse/CAMEL-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565101#comment-17565101
]
Andrea Cosentino edited comment on CAMEL-18208 at 7/12/22 5:06 PM:
---
AWS Secret Manager - DONE
Google Secrets Manager - DONE
was (Author: ancosen):
AWS Secret Manager - DONE
> vault: allow to retrieve a specific secret version/revision
> ---
>
> Key: CAMEL-18208
> URL: https://issues.apache.org/jira/browse/CAMEL-18208
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Minor
>
> The vaults for which we have support in Apache Camel support versioned
> secrets (i.e. [1][2]) and it would be very useful to have an option to
> include the verison/revision of the secret in the vault property syntax, as
> example:
> {{aws:username@123}}
> This would mean to get the secret named username and version 123 from the
> aws vault.
> [1]
> https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
> [2]
> https://learn.hashicorp.com/tutorials/vault/versioned-kv#step-7-configure-automatic-data-deletion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18265) Camel AWS Secret Manager: Source Properties tests should use the test-infra module
Andrea Cosentino created CAMEL-18265: Summary: Camel AWS Secret Manager: Source Properties tests should use the test-infra module Key: CAMEL-18265 URL: https://issues.apache.org/jira/browse/CAMEL-18265 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
[
https://issues.apache.org/jira/browse/CAMEL-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565101#comment-17565101
]
Andrea Cosentino commented on CAMEL-18208:
--
AWS Secret Manager - DONE
> vault: allow to retrieve a specific secret version/revision
> ---
>
> Key: CAMEL-18208
> URL: https://issues.apache.org/jira/browse/CAMEL-18208
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Minor
>
> The vaults for which we have support in Apache Camel support versioned
> secrets (i.e. [1][2]) and it would be very useful to have an option to
> include the verison/revision of the secret in the vault property syntax, as
> example:
> {{aws:username@123}}
> This would mean to get the secret named username and version 123 from the
> aws vault.
> [1]
> https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
> [2]
> https://learn.hashicorp.com/tutorials/vault/versioned-kv#step-7-configure-automatic-data-deletion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18257) Camel-Hashicorp-vault: Support list secrets operation
Andrea Cosentino created CAMEL-18257: Summary: Camel-Hashicorp-vault: Support list secrets operation Key: CAMEL-18257 URL: https://issues.apache.org/jira/browse/CAMEL-18257 Project: Camel Issue Type: New Feature Components: camel-hashicorp-vault Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18256) Camel-Hashicorp-vault: Support Versioning of secret while reading
[ https://issues.apache.org/jira/browse/CAMEL-18256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18256. -- Resolution: Fixed > Camel-Hashicorp-vault: Support Versioning of secret while reading > - > > Key: CAMEL-18256 > URL: https://issues.apache.org/jira/browse/CAMEL-18256 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18256) Camel-Hashicorp-vault: Support Versioning of secret while reading
Andrea Cosentino created CAMEL-18256: Summary: Camel-Hashicorp-vault: Support Versioning of secret while reading Key: CAMEL-18256 URL: https://issues.apache.org/jira/browse/CAMEL-18256 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18176) Create a camel-hashicorp-vault test-infra module
[ https://issues.apache.org/jira/browse/CAMEL-18176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18176. -- Resolution: Fixed > Create a camel-hashicorp-vault test-infra module > > > Key: CAMEL-18176 > URL: https://issues.apache.org/jira/browse/CAMEL-18176 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > > To have a way to test the vault locally -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18178) Create a Camel-hashicorp-vault spring boot starter
[ https://issues.apache.org/jira/browse/CAMEL-18178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18178. -- Resolution: Fixed > Create a Camel-hashicorp-vault spring boot starter > -- > > Key: CAMEL-18178 > URL: https://issues.apache.org/jira/browse/CAMEL-18178 > Project: Camel > Issue Type: Sub-task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18178) Create a Camel-hashicorp-vault spring boot starter
Andrea Cosentino created CAMEL-18178: Summary: Create a Camel-hashicorp-vault spring boot starter Key: CAMEL-18178 URL: https://issues.apache.org/jira/browse/CAMEL-18178 Project: Camel Issue Type: Sub-task Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18176) Create a camel-hashicorp-vault test-infra module
Andrea Cosentino created CAMEL-18176: Summary: Create a camel-hashicorp-vault test-infra module Key: CAMEL-18176 URL: https://issues.apache.org/jira/browse/CAMEL-18176 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.18.0 To have a way to test the vault locally -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17689) Create a Camel Hashicorp Vault Component
[ https://issues.apache.org/jira/browse/CAMEL-17689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551607#comment-17551607 ] Andrea Cosentino commented on CAMEL-17689: -- TODO: - Support reading secrets as operation - Improving docs with examples - Create Spring Boot starter > Create a Camel Hashicorp Vault Component > > > Key: CAMEL-17689 > URL: https://issues.apache.org/jira/browse/CAMEL-17689 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > > https://github.com/spring-projects/spring-vault -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-17689) Create a Camel Hashicorp Vault Component
[ https://issues.apache.org/jira/browse/CAMEL-17689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-17689: - Fix Version/s: 3.18.0 (was: 3.x) > Create a Camel Hashicorp Vault Component > > > Key: CAMEL-17689 > URL: https://issues.apache.org/jira/browse/CAMEL-17689 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.18.0 > > > https://github.com/spring-projects/spring-vault -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create
[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-16287. -- Resolution: Fixed > camel-aws2-sqs should use pagination for deciding which aws sqs queues it > should create > --- > > Key: CAMEL-16287 > URL: https://issues.apache.org/jira/browse/CAMEL-16287 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.3, 3.8.0 >Reporter: Gyorgy Abraham >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.14.4, 3.18.0 > > > There is an auto create queue feature for aws-sqs in camel-sqs component. > Upon camel context creation / route building, it issues an API call to list > all sqs queues, so it skips the creation for already existing ones. If camel > context has a for example consumer route for an sqs queue that is not listed > in the response of this API call, camel will try to to create it. > However, this API only lists the first 1000 queues in the current account. If > there are more then 1000 queues, camel-sqs will try to create a new one, and > might fail. In our company's account, we have 1442 queues in our account and > Camel tried to create a .fifo queue because it thought it wasnt already > existing, resulting in application startup error. > Relevant code: > [https://github.com/apache/camel/blob/master/components/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Endpoint.java#L174] > Relevant API docs at AWS: > [https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/sqs/AmazonSQS.html#listQueues-com.amazonaws.services.sqs.model.ListQueuesRequest-] > Solution is straightforward: use pagination and load all queues. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create
[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542628#comment-17542628 ] Andrea Cosentino commented on CAMEL-16287: -- There is no plan for another 3.17.x release. It's not an LTS. It will be fixed in 3.18.x and LTS. > camel-aws2-sqs should use pagination for deciding which aws sqs queues it > should create > --- > > Key: CAMEL-16287 > URL: https://issues.apache.org/jira/browse/CAMEL-16287 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.3, 3.8.0 >Reporter: Gyorgy Abraham >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.14.4, 3.18.0 > > > There is an auto create queue feature for aws-sqs in camel-sqs component. > Upon camel context creation / route building, it issues an API call to list > all sqs queues, so it skips the creation for already existing ones. If camel > context has a for example consumer route for an sqs queue that is not listed > in the response of this API call, camel will try to to create it. > However, this API only lists the first 1000 queues in the current account. If > there are more then 1000 queues, camel-sqs will try to create a new one, and > might fail. In our company's account, we have 1442 queues in our account and > Camel tried to create a .fifo queue because it thought it wasnt already > existing, resulting in application startup error. > Relevant code: > [https://github.com/apache/camel/blob/master/components/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Endpoint.java#L174] > Relevant API docs at AWS: > [https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/sqs/AmazonSQS.html#listQueues-com.amazonaws.services.sqs.model.ListQueuesRequest-] > Solution is straightforward: use pagination and load all queues. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (CAMEL-18145) camel-aws-secretsmanager - Test failure in rotateSecrets
[ https://issues.apache.org/jira/browse/CAMEL-18145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18145: Assignee: Andrea Cosentino > camel-aws-secretsmanager - Test failure in rotateSecrets > > > Key: CAMEL-18145 > URL: https://issues.apache.org/jira/browse/CAMEL-18145 > Project: Camel > Issue Type: Test > Components: camel-aws >Affects Versions: 3.18.0 >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.18.0 > > > Message History (source location and message history is disabled) > --- > Source ID > Processor Elapsed (ms) > route6/route6 > from[direct://rotateSecret] 29 > ... > route6/to8 > aws-secrets-manager://test?operation=rotateSecret 0 > Stacktrace > --- > software.amazon.awssdk.services.secretsmanager.model.ResourceNotFoundException: > Lambda does not exist or could not be accessed (Service: SecretsManager, > Status Code: 400, Request ID: > KYCVGVN52HR0PX630EFH1HN44VH32JHHJC8DOFTB0GWO9LHG4OIO) > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleErrorResponse(CombinedResponseHandler.java:125) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleResponse(CombinedResponseHandler.java:82) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:60) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:41) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:40) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:30) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:73) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:78) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:40) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:50) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:81) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80) > ~[sdk-core-2.17.198.jar:?] > at >
