knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Added mention of channels to event type autocreate docs (#5639) 

Signed-off-by: Calum Murray <cmurray@redhat.com>
This commit is contained in:
Calum Murray 2023-08-01 05:01:46 -04:00 committed by GitHub
parent b1450fedec
commit a52897a7e7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/eventing/experimental-features/eventtype-auto-creation.md
View File

@ -11,7 +11,7 @@
## Overview
With the `eventtype-auto-creation` feature, we have possibliy to _auto create_ EventTypes that are received and ingressed by the Knative Broker implementations.
With the `eventtype-auto-creation` feature, we have possibliy to _auto create_ EventTypes that are received and ingressed by the Knative Broker and Channel implementations.
For making use of this _opt-in_ feature, we must turn it on in the `config-features`, by setting the `eventtype-auto-creation` flag to `enabled`:
@ -26,10 +26,12 @@ data:
...
```
With this experiemental feature enabled, we get `EventType`s on the broker ingress for free. Instead of manually creating them as yaml manifests along the application code that talks to the `Broker` API.
With this experiemental feature enabled, we get `EventType`s on the broker/channel ingress for free, instead of manually creating them as yaml manifests along the application code that talks to the `Broker` or `Channel` API.
## Example
### Create a Broker
To check the feature is working, create a simple broker:
@ -59,7 +61,7 @@ To check the feature is working, create a simple broker:
Where `<filename>` is the name of the file you created in the previous step.
## Produce Events to the Broker
### Produce Events to the Broker
The auto-creation feature is triggered by processed events. Therefore to verify the functionality we need to send a sample event with desired type. This can be achieved in a severals ways, below are two examples using `kn-plugin-event` and `cURL`
container in a cluster.
@ -98,7 +100,7 @@ container in a cluster.
```
This is more complex, as we have to _craft_ the event as part of the `curl` HTTP POST request.
## Event Discovery
### Event Discovery
After the two produced events, we should be able to have discoverable events in the system, based on the `eventtype-auto-creation` feature: