What is changing?
Advanced trigger filter proposal
In what release will this take happen (to the best of your knowledge)?
0.6
From knative/eventing#930:
Problem
We need more advanced filtering mechanisms than just exact match on Cloud Event types and sources.
Persona:
Event Consumer
Exit Criteria
Being able to configure advanced filters on triggers, either with CEL or some other language.
Suggestions for where to add this content
- Update/add/delete necessary info in https://github.com/knative/docs/tree/release-0.5/docs/eventing/README.md
- And link to new topic (details below)
- Create new Event Trigger topic
- Key focal points to address in the document:
- Try to create sections as follows:
- overview/conceptual content
- Address "why user should use a filter" (ie. Use a filter in your event trigger to reduce and filter out only the attributes of an event that you want sent to the event subscribers.)
- requirements/prerequisites (create a "Before you begin" section)
- list all requirements and link to relevant content
- Link to CEL -> explain (ie. Trigger filters support expressions written in CEL.)
- "how to" info (the "task-oriented" step by step details for creating an event filter in a trigger) -> use a gerund in title (for example Filtering event attributes)
- Example(s) (show them how and where they would/can create a filter in their trigger) i see lots in the proposal and it would be most consumable if we could organize these to some degree
- Link to what the next logical step would be (and include links to related info) to keep the user moving forward
What is changing?
Advanced trigger filter proposal
In what release will this take happen (to the best of your knowledge)?
0.6
From knative/eventing#930:
Problem
We need more advanced filtering mechanisms than just exact match on Cloud Event types and sources.
Persona:
Event Consumer
Exit Criteria
Being able to configure advanced filters on triggers, either with CEL or some other language.
Suggestions for where to add this content