This is awesome. Thanks James for sharing it. -r
> On Feb 8, 2019, at 12:11 PM, James Thomas <[email protected]> wrote: > > Hello Whiskers. > > On Wednesday's Community Call, I presented my work on building a "pluggable > trigger feed event provider". The background for this experiment was > needing to build another trigger feed event source without having to > replicate all the boilerplate needed for trigger management. > > Here is the presentation from the call: > https://speakerdeck.com/jthomas/apache-openwhisk-pluggable-event-providers > Video recording of the call is available on the OpenWhisk YouTube channel: > https://www.youtube.com/watch?v=krm7X5YpGy0 > > Feedback on the call was very positive so I've pushed the code to an > external Github repo allowing others to have a look at how it works. > > This is the repo for the "generic event feed provider". The README contains > all the instructions on how to create a plugin and run the provider with a > pluggable event source. > > https://github.com/jthomas/openwhisk-pluggable-event-provider > > Here's an example event plugin I built for an S3-compatible object store. > It polls a bucket endpoints and compares file etags, stored in Redis, to > determine any file changes. Triggers are fired with file events. > > https://github.com/jthomas/openwhisk-s3-trigger-feed > > As discussed on the call, my next steps were.... > > - > > Make the code public for the community to evaluate. (DONE ✅) > - > > Write a few more plugin providers (RabbitMQ, MQTT) to test it further. > - > > Contribute the code back to Apache to become an official component of > the project. > > All feedback welcome! > -- > Regards, > James Thomas
