-
Notifications
You must be signed in to change notification settings - Fork 630
very draft roadmap #46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| Eventing Roadmap | ||
|
|
||
| # 0.1 | ||
|
|
||
| A. Ability to register an event sources and specify which events may be generated from that source [Proposal](https://github.com/elafros/eventing/issues/39) | ||
| B. kubctl command to set up a trigger where a specific event will cause a specific action | ||
| C. Example source generating an event | ||
| D. Example action | ||
| E. Events conform to CloudEvent 0.1 specification | ||
|
|
||
| # 0.2 | ||
|
|
||
| A. A local event can trigger a Google Cloud Function | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. FYI: We may need help from GCF on this. Found out this week that the "CallFunction" API always makes up a fake event context.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +inlined@ I assumed we would trigger an HTTP Function and just pass it an event, then include a JS library to make it "feel" like an event |
||
| B. A Google source can trigger a local action | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. May make it clear that this is a conceptual demo and is allowed to use architectural scaffolding (e.g. deploy a cloud function that forwards the webhook to the event cluster) |
||
|
|
||
| # 0.3 | ||
|
|
||
| A. Pipeline the output of one action into the input of another | ||
|
|
||
| # 0.4 | ||
|
|
||
| A. an action may accept a stream interface to process many events at once | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is just a nit, but we might clarify how this is different from the batch like interface that could also accept many events at once. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
specific action powered by a specific processor