Pierangelo Di Pilato

I'm looking for how batch support would impact the event delivery section of the spec: https://github.com/knative/specs/blob/main/specs/eventing/data-plane.md#event-delivery, the different approaches we could have and pros and cons for each.

I get the difference (that it is also why I commented with related and not duplicated), one option that you have is having a service that splits a single event...

/remove-lifecycle stale /triage accepted

This is similar to the @creydr feature extension about OAuthSource/Sink outlined here https://docs.google.com/document/d/1e7UgNTkL0Br5Da09Rg2ieVmhKJo4VXuBj-mHT9NCujY/edit#heading=h.a9ka3es7ol9v and I think it's useful to have. It also helps with connecting other systems (including AWS eventbridge...

@Cali0707 any updates on this one?

I think the challenge is RBAC, if we allow referencing Brokers in different namespaces, how do we know if the user that has access to create triggers in namespace X...

So for this, we would need a [feature track document](https://github.com/knative/community/blob/main/mechanics/FEATURE-TRACKS.md) that describes in more detail how RBAC would work and how someone allows or disallow a namespace to access another...

I will add triage-accepted label to make sure this doesn't get closed as I think it would be a great addition and many have asked for this but the design...

Hi @giggio, would you mind providing your input to the issues above and whether the proposal would work for your use cases?

Hi @satyampsoni, no, that's really just a POC, the work required for this issue to be completed in larger and requires more capacity