Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions roadmap.md
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
Copy link
Copy Markdown
Contributor

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

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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The 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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The 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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The 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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The 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.