christophd commented on issue #1834:
URL: https://github.com/apache/camel-k/issues/1834#issuecomment-1020980594
@lburgazzoli sure!
but isn't this covered already by Kamelets?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
christophd commented on issue #1834:
URL: https://github.com/apache/camel-k/issues/1834#issuecomment-1020997613
So in terms of an eventing source a KameletBinding defines a Kamelet as a
binding source and a channel/broker as a sink within the binding. This approach
has replaced the former
christophd commented on issue #1834:
URL: https://github.com/apache/camel-k/issues/1834#issuecomment-1021013273
we are not able to use a Knative Trigger directly in a KameletBinding in
order to filter the events that are consumed by the sink. We need to have a
channel that the KameletBindi
christophd commented on issue #1834:
URL: https://github.com/apache/camel-k/issues/1834#issuecomment-1021049348
sounds like a valuable option
--
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
christophd commented on issue #1834:
URL: https://github.com/apache/camel-k/issues/1834#issuecomment-1020980594
--
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.
To unsubscri
christophd commented on issue #1834:
URL: https://github.com/apache/camel-k/issues/1834#issuecomment-1022062878
I like the idea to auto create the knative service resource `telegram-sink`
as part of the KameletBinding. Feels more natural and makes the usage of the
channel obsolete.
