Skip to content

Commit

Permalink
Update blog/docs/articles/knative-eventing-vision.md
Browse files Browse the repository at this point in the history 
Co-authored-by: Christoph Stäbler <cstabler@redhat.com>
  • Loading branch information
@matzew @creydr
matzew and creydr authored Jul 26, 2023
1 parent cf06f2b commit 37e841a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion blog/docs/articles/knative-eventing-vision.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ In order to improve the developer experience of Knative Eventing we are enhancin

Today the EventType API is limited to Source-Duck compliant sources, and only usable in combination with the Knative Broker API.

However when using the broker with 3rd party integration, such as regular deployments or even CLI tools like “kn event send” it does not work! We do not see any EvenType information for these common usage patterns.
However when using the Broker with a 3rd party integration, such as regular deployments or even CLI tools like `kn event send` the EventType is not created automatically! We do not see any EvenType information for these common usage patterns.
To address this problem we introduce an optional feature flag which can be ENABLED in order to have support for an automatic creation of EventTypes.

Details can be found in the matching [feature track document](https://docs.google.com/document/d/1H8-mkMs5HWd3U7TT6KAWgU9ltDxqZv25Wls-6c4lneA/edit).
Expand Down

0 comments on commit 37e841a

Please sign in to comment.