[jira] [Assigned] (CAMEL-13407) CouchDbChangesetTracker fails silently on network error and does not recover
[ https://issues.apache.org/jira/browse/CAMEL-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu reassigned CAMEL-13407: Assignee: Ramu > CouchDbChangesetTracker fails silently on network error and does not recover > > > Key: CAMEL-13407 > URL: https://issues.apache.org/jira/browse/CAMEL-13407 > Project: Camel > Issue Type: Bug > Components: camel-couchdb >Affects Versions: 2.21.5 >Reporter: Simon Temple >Assignee: Ramu >Priority: Major > Fix For: 2.23.3 > > Attachments: CouchDbChangesetTracker.java > > Original Estimate: 4h > Remaining Estimate: 4h > > We ran into this in production when a network error made the CouchDB instance > unavailable for a short while. > We were running with camel 2.18.1 so I patched a local copy of the component; > which has been running without problems for many weeks now. > I'd like to propose our code as the fix to this. > We're now running with 2.23.1 so would be looking for a 2.x fix -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13407) CouchDbChangesetTracker fails silently on network error and does not recover
[ https://issues.apache.org/jira/browse/CAMEL-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815896#comment-16815896 ] Ramu commented on CAMEL-13407: -- [~simon.tem...@amalto.com] could you please attach a simple junit test for the changes > CouchDbChangesetTracker fails silently on network error and does not recover > > > Key: CAMEL-13407 > URL: https://issues.apache.org/jira/browse/CAMEL-13407 > Project: Camel > Issue Type: Bug > Components: camel-couchdb >Affects Versions: 2.21.5 >Reporter: Simon Temple >Priority: Major > Fix For: 2.23.3 > > Attachments: CouchDbChangesetTracker.java > > Original Estimate: 4h > Remaining Estimate: 4h > > We ran into this in production when a network error made the CouchDB instance > unavailable for a short while. > We were running with camel 2.18.1 so I patched a local copy of the component; > which has been running without problems for many weeks now. > I'd like to propose our code as the fix to this. > We're now running with 2.23.1 so would be looking for a 2.x fix -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13401) Create a webhook meta-component
[
https://issues.apache.org/jira/browse/CAMEL-13401?focusedWorklogId=226107=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-226107
]
ASF GitHub Bot logged work on CAMEL-13401:
--
Author: ASF GitHub Bot
Created on: 11/Apr/19 16:04
Start Date: 11/Apr/19 16:04
Worklog Time Spent: 10m
Work Description: nicolaferraro commented on pull request #2867:
CAMEL-13401: adding a webhook meta-component and first implementation with
Telegram
URL: https://github.com/apache/camel/pull/2867
As per subject. This adds the capability for components to self register to
receive push notifications instead of doing polling.
Registration is automatic by default, but it will be disabled in camel k
where there will be a specific process to register webhooks.
In knative, components supporting webhooks can scale to 0 ;)
There are few things I'm not sure about... for example, the
`MultiRestConsumer` class.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 226107)
Time Spent: 10m
Remaining Estimate: 0h
> Create a webhook meta-component
> ---
>
> Key: CAMEL-13401
> URL: https://issues.apache.org/jira/browse/CAMEL-13401
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The intention is to create a meta-component that allows other components to
> define how they can configure themselves to create push-based consumers by
> remotely configuring a webhook.
> The way it's used is similar to the master component.
>
> E.g.
> The following route starts from a Telegram polling consumer:
> {code:java}
> from("telegram:bots/token")
> .to("log:info"){code}
>
> By prepending the _webhook_ uri prefix, we literally _prepend a webhook
> listener_ to it:
> {code:java}
> from("webhook:telegram:bots/token")
> .to("log:info"){code}
>
> The role of the webhook meta-component is of:
> * Exposing one or more endpoints using the rest consumer factory
> * Running the delegate endpoint in webhook mode (each component defines the
> specific rules)
> * Registering the webhook at the webhook provider site (specific per
> component, external URL configurable)
> * Unregistering the webhook at the webhook provider site when it's no more
> necessary (specific per component)
> So, the meta-component sets up the infrastructure and orchestrates the
> workflow.
>
> Registration/deregistration should be configurable:
> * In standalone mode, the registration is done at route startup, the
> deregistration is done at route shutdown
> * In Camel K mode, automatic registration is disabled by default, because
> the deployment can be scale up/down (especially in Knative mode, where this
> happens automatically):
> ** Camel K will setup a webhook subscription resource that takes care of
> externally registering/deregistering the webhook when the integration is
> created/edited/deleted (will use the webhook component API for this)
>
> With this meta-component, in Camel K + Knative mode, we can create
> integrations from telegram, slack, github, twitter, dropbox, that can
> scale down to 0 when not used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13408) Investigate camel-jibx
John Poth created CAMEL-13408: - Summary: Investigate camel-jibx Key: CAMEL-13408 URL: https://issues.apache.org/jira/browse/CAMEL-13408 Project: Camel Issue Type: New Feature Components: camel-jibx Reporter: John Poth Tests for camel-jibx have been [disabled|https://github.com/apache/camel/blob/b93c32756fe097163bf3cd642f53ecc30b457f8e/components/camel-jibx/pom.xml#L151] for a while. JDK-8 [support|https://github.com/jibx/jibx/issues/3] was added in 1.3.1 but it seems it's not a simple upgrade. JDK9+ support is still an open [issue|https://github.com/jibx/jibx/issues/9] So we should either mark the component as deprecated in 2.x and remove it in 3.x or try to fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13407) CouchDbChangesetTracker fails silently on network error and does not recover
[ https://issues.apache.org/jira/browse/CAMEL-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13407: - Priority: Major (was: Critical) > CouchDbChangesetTracker fails silently on network error and does not recover > > > Key: CAMEL-13407 > URL: https://issues.apache.org/jira/browse/CAMEL-13407 > Project: Camel > Issue Type: Bug > Components: camel-couchdb >Affects Versions: 2.21.5 >Reporter: Simon Temple >Priority: Major > Fix For: 2.23.3 > > Attachments: CouchDbChangesetTracker.java > > Original Estimate: 4h > Remaining Estimate: 4h > > We ran into this in production when a network error made the CouchDB instance > unavailable for a short while. > We were running with camel 2.18.1 so I patched a local copy of the component; > which has been running without problems for many weeks now. > I'd like to propose our code as the fix to this. > We're now running with 2.23.1 so would be looking for a 2.x fix -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13407) CouchDbChangesetTracker fails silently on network error and does not recover
Simon Temple created CAMEL-13407: Summary: CouchDbChangesetTracker fails silently on network error and does not recover Key: CAMEL-13407 URL: https://issues.apache.org/jira/browse/CAMEL-13407 Project: Camel Issue Type: Bug Components: camel-couchdb Affects Versions: 2.21.5 Reporter: Simon Temple Fix For: 2.23.3 Attachments: CouchDbChangesetTracker.java We ran into this in production when a network error made the CouchDB instance unavailable for a short while. We were running with camel 2.18.1 so I patched a local copy of the component; which has been running without problems for many weeks now. I'd like to propose our code as the fix to this. We're now running with 2.23.1 so would be looking for a 2.x fix -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13407) CouchDbChangesetTracker fails silently on network error and does not recover
[ https://issues.apache.org/jira/browse/CAMEL-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Temple updated CAMEL-13407: - Attachment: CouchDbChangesetTracker.java > CouchDbChangesetTracker fails silently on network error and does not recover > > > Key: CAMEL-13407 > URL: https://issues.apache.org/jira/browse/CAMEL-13407 > Project: Camel > Issue Type: Bug > Components: camel-couchdb >Affects Versions: 2.21.5 >Reporter: Simon Temple >Priority: Critical > Fix For: 2.23.3 > > Attachments: CouchDbChangesetTracker.java > > Original Estimate: 4h > Remaining Estimate: 4h > > We ran into this in production when a network error made the CouchDB instance > unavailable for a short while. > We were running with camel 2.18.1 so I patched a local copy of the component; > which has been running without problems for many weeks now. > I'd like to propose our code as the fix to this. > We're now running with 2.23.1 so would be looking for a 2.x fix -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13398) Camel-AWS-*: Lets adopt the same approach as CAMEL-12936 for all the components
[ https://issues.apache.org/jira/browse/CAMEL-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13398. -- Resolution: Fixed > Camel-AWS-*: Lets adopt the same approach as CAMEL-12936 for all the > components > --- > > Key: CAMEL-13398 > URL: https://issues.apache.org/jira/browse/CAMEL-13398 > Project: Camel > Issue Type: Task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13402) Update to Californium 2.0.x and support DTLS
[ https://issues.apache.org/jira/browse/CAMEL-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815278#comment-16815278 ] Colm O hEigeartaigh commented on CAMEL-13402: - Yep I'm still working on it. I'll submit a PR for review when I'm done. > Update to Californium 2.0.x and support DTLS > > > Key: CAMEL-13402 > URL: https://issues.apache.org/jira/browse/CAMEL-13402 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > This task is to update to Californium 2.0.x and support DTLS in the > camel-coap component. Currently we only support plain UDP and not UDP / TLS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13402) Update to Californium 2.0.x and support DTLS
[ https://issues.apache.org/jira/browse/CAMEL-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815249#comment-16815249 ] Andrea Cosentino commented on CAMEL-13402: -- It's not yet merged. There is only a branch. > Update to Californium 2.0.x and support DTLS > > > Key: CAMEL-13402 > URL: https://issues.apache.org/jira/browse/CAMEL-13402 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > This task is to update to Californium 2.0.x and support DTLS in the > camel-coap component. Currently we only support plain UDP and not UDP / TLS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13402) Update to Californium 2.0.x and support DTLS
[ https://issues.apache.org/jira/browse/CAMEL-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815244#comment-16815244 ] Claus Ibsen commented on CAMEL-13402: - Is there more work to this or can this ticket be resolved > Update to Californium 2.0.x and support DTLS > > > Key: CAMEL-13402 > URL: https://issues.apache.org/jira/browse/CAMEL-13402 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > This task is to update to Californium 2.0.x and support DTLS in the > camel-coap component. Currently we only support plain UDP and not UDP / TLS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11030) Add a vault service to manage secrets
[
https://issues.apache.org/jira/browse/CAMEL-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815243#comment-16815243
]
Claus Ibsen commented on CAMEL-11030:
-
No the work has not started. Use the vote system in JIRA to help prioritze the
tickets
> Add a vault service to manage secrets
> -
>
> Key: CAMEL-11030
> URL: https://issues.apache.org/jira/browse/CAMEL-11030
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.0.0
>
>
> Lot of components these days are supposed to manage secrets such as auth
> tokens etc. but as there's no common support in camel each component is
> implementing the same concept which increase the maintenance cost.
> It would be nice to have a vault service in camel-core so that components can
> leverage and extend it, some ideas/examples:
> - to store auth tokens and delegate to the vault the notification about
> expiration and renewal when needed (by registering some functions/callbacks)
> - to provide different backends like kubernetes secrets, hashicorp's vault,
> - to provide different workflow (i.e. JSON Web Token)
> - to use the vault as properties source if someone prefix a property with
> vault like {{vault:db.password}}
> The interface should be as simple as possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-11030) Add a vault service to manage secrets
[
https://issues.apache.org/jira/browse/CAMEL-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815222#comment-16815222
]
Daniel del Castillo commented on CAMEL-11030:
-
Any updates on this ticket? I'm looking to read secrets, not just credentials,
from Vault and then use them downstream in the route. I think a {{vault:}}
component may be most suitable for this?
> Add a vault service to manage secrets
> -
>
> Key: CAMEL-11030
> URL: https://issues.apache.org/jira/browse/CAMEL-11030
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.0.0
>
>
> Lot of components these days are supposed to manage secrets such as auth
> tokens etc. but as there's no common support in camel each component is
> implementing the same concept which increase the maintenance cost.
> It would be nice to have a vault service in camel-core so that components can
> leverage and extend it, some ideas/examples:
> - to store auth tokens and delegate to the vault the notification about
> expiration and renewal when needed (by registering some functions/callbacks)
> - to provide different backends like kubernetes secrets, hashicorp's vault,
> - to provide different workflow (i.e. JSON Web Token)
> - to use the vault as properties source if someone prefix a property with
> vault like {{vault:db.password}}
> The interface should be as simple as possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
