Knowing who created an event in an event-driven system introduces a coupling that event driven systems aims to remove in the first place.
It would be ideal for consumers of an event to simply specify during a release, that there must be one or more providers that publish a particular event type.
The can-i-deploy check would then ask a question like this:
"Is there a provider in that produces compatible with schema ?"
Knowing who created an event in an event-driven system introduces a coupling that event driven systems aims to remove in the first place. It would be ideal for consumers of an event to simply specify during a release, that there must be one or more providers that publish a particular event type. The that produces compatible with schema ?"
can-i-deploy
check would then ask a question like this: "Is there a provider inhttps://pact.canny.io/admin/board/feature-requests/p/support-messages-without-knowing-who-the-provider-is