CloudEvents

Said goodbye to the CloudEvents group, I am moving on and will have a lot less time to be able to be involved. It was a ton of fun maintaining the sdk for go. Interested to join?

Also, found out @duginabox clicks links during the @CloudEventsIO meeting 🤣 https://t.co/nwXiYdtMaM

We're thrilled to have @p_mbanugo joining us at KubeHuddle to deliver his workshop about serverless on Kubernetes.

This is a fantastic opportunity to get hands-on experience with @KnativeProject and @CloudEventsIO

Limited tickets available

https://t.co/n9TgRPEZWr

Twitter feed image.

@ibuildthecloud No link to @CloudEventsIO yet but I think defining the events would be good and then defining the sub APIs based on the CE's new specs would be a great test case.
Having an option for a PaaS to auto update would be neat. @KnativeProject

Great to see @AsyncAPISpec and @CloudEventsIO shout out at @LEGOEngineering 🍻😍

Twitter feed image.

@s0enke @donkersgood @boyney123 @nickste @sheenbrisals Ideally this should be part of the message, ie transport independent. See @CloudEventsIO sequence attribute as an example https://t.co/y1kxClc62Q

[New Post] Transforming a non-CloudEvent into a @CloudEventsIO using a webhook function running on @VMWEventBroker/@KnativeProject. I used the @project_harbor webhook notification feature as a use case.
🙏 @embano1 #eventdriven #automation #serverless
https://t.co/PuH8w5SAuj

Twitter feed image.

Twitter feed image.

Seeing a lot more interest in PS/PCLI in function runtimes, too!

And if you use @CloudEventsIO in your APIs there‘s even a PS SDK https://t.co/wGhfdFge9E 🤩 https://t.co/n0UiDSGtI3