Matthias Wessendorf
Matthias Wessendorf
@g1rjeevan sounds good! Feel free to join our slack instance for further discussions
Related: https://github.com/knative/eventing/issues/2750
Just tested this: ``` k get eventtypes.eventing.knative.dev NAME TYPE SOURCE SCHEMA REFERENCE NAME REFERENCE KIND DESCRIPTION READY REASON dev.knative.source.github.push-v1b1 dev.knative.source.github.push https://github.com/knative/eventing default Broker dev.knative.source.github.push-v1b2 dev.knative.source.github.push https://github.com/knative/eventing ``` both brokers are...
@Cali0707 we have some API tests for that, I did tweak them a bit, as their naming was a bit confusing, given the old behavior, see here: https://github.com/knative/eventing/pull/8030
Fix for this was here: * https://github.com/knative/eventing/pull/8087 * https://github.com/knative/eventing/pull/8097 (little addon) * https://github.com/knative/eventing/pull/8079
That would imply some TTL of the event as well as there is potential race when a number of "data plane receivers" (ingress) are updating the status of the one...
Raul, thanks for the PR, I will take a look - but I am not atm if this repo is the best option. But yeah, there is already a websocket...
@dprotaso yeah, not blocked but moving slow. but we are on it
@lkingland I was just checking the same :smile: