You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by GitBox <gi...@apache.org> on 2019/04/09 08:59:27 UTC

[GitHub] [camel-k] nicolaferraro opened a new issue #597: Support new Camel 3 webhooks

nicolaferraro opened a new issue #597: Support new Camel 3 webhooks
URL: https://github.com/apache/camel-k/issues/597
 
 
   Camel part: https://issues.apache.org/jira/browse/CAMEL-13401
   
   From the issue:
   > 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.
   
   
   We should figure out what's the best strategy, but at high level Camel K should define a new custom resource e.g. `WebhookRegistration` that will create a pod with the role of configuring the routes as in the main integration but not starting them: routes will be used to register/deregister all webhooks.
   Deregistration will be triggered by a finalizer in the `WebhookRegistration` resource.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services