You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2019/10/09 10:46:32 UTC
[GitHub] [camel-k-runtime] nicolaferraro opened a new issue #151: Support
Knative broker/trigger model
nicolaferraro opened a new issue #151: Support Knative broker/trigger model
URL: https://github.com/apache/camel-k-runtime/issues/151
We can add a third endpoint to knative called `events`.
A user can write:
```
from('knative:events/chuck.norris')
```
To get all events of type `chuck.norris`.
The behavior will be:
- The operator creates a trigger on event type `chuck.norris`
- The component filters messages containing header `Ce-Type` equals to `chuck.norris`
- The component exposes the usual endpoint to receive cloud events
Some additional properties are required:
- `brokerApiVersion`: to change the api version of the broker (interpreted by the operator)
- `brokerName`: to change the name of the broker to use (by default there's only one called default)
- brokerKind cannot be changed as there's a single CRD at the moment
Additional filters can be put in the endpoint, e.g.:
```
from('knative:events/chuck.norris?ceAuthorName=Nicola')
```
`ceAuthorName` like filters can be dynamic and translate into an additional filter on both the trigger and the component on the header `Ce-Author-Name`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services