-
Notifications
You must be signed in to change notification settings - Fork 37
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
Propose to add CNCF CloudEvents webhook standards #51
Comments
Thanks for sharing @gowrizrh :) Any contribution is welcome! I started digging thru cloudevents and found this. Is this a good representation of how cloudevents aims to help on webhooks? If yes, I'll include that on the standardization effort. |
That's right. It also might be worth reading through the the main spec which should cover topics around event / payload schemas. The webhooks specification you linked should be an extension of the main spec with more things covering rate limiting and retries. |
Hi @gowrizrh . I added CloudEvents to the standardization efforts. Thanks again for the contribution and for making the world a better place for webhooks! <3 PS: Are you in the CloudEvents working group? |
Thank you 😀 No I'm not in the working group |
Just found this thread and will probably file another PR to update the section. E.g. CE v1 is finalized and stable. Also, CE offers several benefits, including SDKs, transport bindings (Kafka, RabbitMQ, HTTP, etc.) and encoding formats (JSON, Avro, Protobuf) which developers can take advantage of instead of reinventing the wheel (error-prone bespoke formats and SDKs). |
This is a proposal to add CloudEvents under the "Standardisation Efforts" section.
CloudEvents is a CNCF incubating project.
https://cloudevents.io
It provides specification on message modelling and event payload design multiple protocols from AQMP to HTTP and HTTP Webhooks.
This could also cover a fair bit on #33
I'll be happy to contribute to this one.
The text was updated successfully, but these errors were encountered: