You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Referencing the existing eventmesh-webhook module and its documentation, support the following functionalities:
Utilize the HTTP Source Connector as a Webhook server, capable of receiving event deliveries from most third-party platforms using a common Webhook protocol, such as UptimeRobot/Better Stack Uptime, Discord, and more.
Support the GitHub Webhook protocol, allowing users to implement non-standard Webhook protocols for specific third-party platforms on their own (for example, refer to org.apache.eventmesh.webhook.receive.protocol.GithubProtocol. Another third-party platform can be supported by implementing the AnotherProtocol class).
"1+n" protocol support: 1 for a common standard Webhook protocol, and n for special non-standard Webhook protocols. Users need to select a protocol in the source-config.yml.
Pil0tXia
changed the title
Use the existing implementation of Webhook as an enhancement to the HTTP Source Connector, needs to be able to support the user's own implementation of a customized Webhook protocol.
[Feature] Add Webhook support for HTTP Source Connector
Apr 30, 2024
Search before asking
Feature Request
This issue is a subtask of #4825.
Referencing the existing
eventmesh-webhook
module and its documentation, support the following functionalities:org.apache.eventmesh.webhook.receive.protocol.GithubProtocol
. Another third-party platform can be supported by implementing theAnotherProtocol
class)."1+n" protocol support: 1 for a common standard Webhook protocol, and n for special non-standard Webhook protocols. Users need to select a protocol in the
source-config.yml
.Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: