[CON-88] Incoming idempotent webhooks about convoy

[binaryfire]

@subomi Yeah, I think that makes sense. That would allow you to use any part of the request (headers or specific JSON keys) as the idempotent key.

[subomi]

Hey @binaryfire ,

This has shipped in the latest release! And we just launched it here

[subomi]

Thanks @binaryfire ,

You're correct. Convoy will process each event independently. This feature is a little trickier to implement, which is counterintuitive to what I expected. The problem is identifying the idempotent key to use because various providers implement this feature differently, Let's take 3 examples:

1. Stripe: The Idempotent key is included in the request body. So you'll need to retrieve the id field from the request payload. See the docs.
2. Adyen: The Idempotent key is a combination of eventCode and pspReference. So we'll need to extract both values and create a unique constraint out of them. See the docs.
3. GitHub: The Idempotent key is the HTTP Header: X-GitHub-Delivery. See the docs.

Of all the implementations, GitHub is the easiest to implement; we can open up a form field on the source configuration to specify the header to act as the idempotent key, but this doesn't work for all use cases. I suggest we'll need to implement a "request matching dsl" to match the different patterns to accommodate different provider's idempotency key implementation.

What do you think?