christophd commented on issue #5529: URL: https://github.com/apache/camel-k/issues/5529#issuecomment-2148064668
@squakez I think this is not the same as [apache/camel-k-runtime/issues/536](https://github.com/apache/camel-k-runtime/issues/536). Yes, we have had problems with the broker name (e.g. when using a customized broker name other than default) and this one has been fixed already. This one here is different. The type information mentioned here refers to the cloud event type information that is used to filter the event stream. In a Pipe users currently need to set this event type in order to filter the event stream, but it is totally valid to read all events from a broker without any type filter. We need to fix the Trigger filter that is created as part of Camel K Knative traits to allow users to get the full event stream without any filter. -- 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 unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
