Matthias Wessendorf
Matthias Wessendorf
/test reconciler-tests
/test reconciler-tests
This could lead to a number of event types, like: ``` k get eventtypes.eventing.knative.dev -n foobar NAMESPACE NAME TYPE SOURCE REFERENCE NAME REFERENCE KIND foobar com.custom.event.orders com.custom.event.orders /system/id/$ID foobar com.custom.event.orders-xyz...
Alternative: different CRD for pure definitions (`(Cluster)EventDefinition`). But that's something to explore if the above changes are no enough
A wip PR is here: #7313 (but type bump etc is needed first)
Why would you want to increase the complexity, that developers, in their services, need to say `is reply` when creating new events. Any event produced is a new event, IMO....
How bad is that really... if we have `n` _identical_ event types (e.g. where source/type) match. I think some "user interface" or "tool", would anyways de-duplicate those (and likely ignore...
I really like setting the `reference` to the CRD, like: ```yaml reference: apiVersion: apiextensions.k8s.io/v1 kind: CustomResourceDefinition name: pingsources.sources.knative.dev ``` in "generic" cases, instead of allowing _no_ reference. Thanks for closing...
/retest
/retest