From 3cfd2c5d2b80ae4b3dfabc5014412e1a638ed1fe Mon Sep 17 00:00:00 2001 From: Matthias Wessendorf Date: Wed, 26 Jul 2023 15:53:58 +0200 Subject: [PATCH] One more suggestion, regarding duck sources Signed-off-by: Matthias Wessendorf --- blog/docs/articles/knative-eventing-vision.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/docs/articles/knative-eventing-vision.md b/blog/docs/articles/knative-eventing-vision.md index fefcf0b099..7716ec6b0a 100644 --- a/blog/docs/articles/knative-eventing-vision.md +++ b/blog/docs/articles/knative-eventing-vision.md @@ -48,7 +48,7 @@ Event discovery helps developers to understand which events they can consume and Knative defines an EventType API which allows for discovery of the types of events that are available in the Knative Eventing system. This helps developers understand what kinds of events can be listened to and processed, which can be particularly helpful in systems with a large number of events being produced. -However currently the EventType is unfortunately underused and is limited to Source-Duck compliant sources, in combination with the Knative Broker API. +However currently the EventType is unfortunately underused and is limited to sources which implement the [Knative Source Ducktype](https://github.com/knative/pkg/blob/aef227e72ead466e1ff7a5dddca2c171b0d5f128/apis/duck/v1/source_types.go#L40), in combination with the Knative Broker API. In order to improve the developer experience of Knative Eventing we are enhancing the event discovery in a couple of ways!