Open sspeiche opened 4 years ago
Maybe the upstream discussion of how eventing is going to be integrated into kn
might be useful in this context: https://docs.google.com/document/d/1B8VK-5nuxt3D-i1Up3onmUbzcztQXE0GRgf1lfx49P8/edit
It's mostly about managing source, where three types of sources as distinguished:
kn
)Currently has support for all built-in source, the first plugins (for KafkaSource and GitHub source are currently developed (within https://github.com/knative/client-contrib), but the untyped sources are still in the conceptual phase.
For synergy with odo I could imagine:
kn
plugin support for reusing kn based source pluginsHappy to discuss how the work from the Knative upstream client can possibly be leveraged here. I would especially recommend joining the discussion around UI related meta-data (the issues linked above), to add the odo
perspective there.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/lifecycle frozen
Description
As a developer, I want a simple way to "subscribe" to an event source so that I can register my serverless function as an event handler.
Acceptance criteria
odo
user to discover various event sources.odo
user to "link" or subscribe from a source to a target.