From 226d47d60e3bb5e6f76aa24d835b52c32f18415c Mon Sep 17 00:00:00 2001 From: Matthias Wessendorf Date: Wed, 26 Jul 2023 14:11:48 +0200 Subject: [PATCH] Update blog/docs/articles/knative-eventing-vision.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Christoph Stäbler --- 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 3da6e26ef6..140d7a1964 100644 --- a/blog/docs/articles/knative-eventing-vision.md +++ b/blog/docs/articles/knative-eventing-vision.md @@ -67,7 +67,7 @@ Details can be found in the matching [feature track document](https://docs.googl ### Support for more than just Brokers -The EventType API will deprecate the “broker” field and replace it with a “reference”, which can be any Knative Resource, such a Channel, a Sink, or even a Database. +The EventType API will deprecate the `.spec.broker` field and replace it with a `.spec.reference`, which can be any Knative Resource, such a Channel, a Sink, or even a Database. The good news is: This breaks the limitation to only use the event type metadata with the Broker API only. Even when there is no filter on Channel/Subscription APIs, it is still important to know what event types are emitted to components like channels or sinks!