Notify as CloudEvent #19
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
sender
Issue related to the send capability
Milestone
Currently, the Deveel.Webhooks library supports webhook notifications in a variety of formats, including JSON and XML.
This feature request is to add support for CloudEvents, a standard format for describing event data in a common way. CloudEvents make it easier to build event-driven systems that are interoperable across different platforms and services.
Background: Webhooks are a mechanism for notifying an application or service about events that occur in another application or service. They are commonly used for integrating third-party services and applications with each other. However, there is no standard format for webhook payloads, which can make it difficult to integrate different services and applications. In response to this problem, the Cloud Native Computing Foundation (CNCF) created the CloudEvent standard in 2018. CloudEvents provide a way to describe event data in a common format, making it easier to build event-driven systems that can work with different services and platforms.
Expected Deliverables - The contributor will need to modify the Deveel.Webhooks library to support CloudEvents as a notification format. This will involve adding a new class to handle CloudEvent payloads, as well as modifying the existing webhook notification code to use the CloudEvent format when requested. The contributor will also need to update the library documentation to reflect the new capability.
Difficulty Level - Moderate - The contributor will need to have some familiarity with the CloudEvent standard and how it is used. However, there are plenty of resources available to help them understand the standard and how to use it.
Resources - The following resources may be helpful for the contributor:
Contact Information: If you have any questions or need guidance, please reach out to me at [antonello at deveel dot com].
The text was updated successfully, but these errors were encountered: