Webhooks: Show Endpoint URL in event log table

[birkjernstrom]

Description

Show the endpoint url we send webhooks to in the log. Helpful confirmation & for debugging of which endpoint received a given webhook.

[birkjernstrom]

@MustaphaHamida Shared this on Discord (let's continue the discussion there), but the URL provided above on your end responds with a HTTP 307 /signup redirect. Probably some authentication middleware that protects the route that you need to configure/change to allow the endpoint to be publicly available, but using our webhook secrets & validating the signature for security.

$ curl -vvv -X POST https://app.ranklly.com/api/webhook/polar

... redacted... 
< HTTP/2 307
< date: Wed, 13 Nov 2024 20:46:22 GMT
< location: /signup
< server: railway-edge
< x-railway-request-id: xTi5qLIBSj6Q9QY9ragzbQ_3500563535
<
* Connection #0 to host app.ranklly.com left intact
/signup%```

[smokyabdulrahman]

@birkjernstrom I can take this up

[smokyabdulrahman]

server part should be ready for review: #4802 🙏

[smokyabdulrahman]

I am starting to feel that I am heading towards the wrong direction.
I would love some clarification of what is needed?

My understanding is that we need to show for each webhook delivery the endpoint that that webhook attempted to call.
However, in the WebhookDelivery model, we only have a foreign key to WebhookEndpoint.
This means if someone updates a WebhookEndpoint, we wouldn't know old WebhookDeliveries called which endpoint.

Thus, we need to add a column to WebhookDelivery to store the endpoint that was called at that point of time.

Second part, showing that in the UI, how do you want to show that? (Example photo attached)

1. show it as a new column in the deliveries table in the UI
2. show it in the details section of the delivery (after clicking on a row in the table - it expands to show extra info including the webhook endpoint that we are going to add)

[smokyabdulrahman]

I would appreciate an update regarding the wanted direction for this issue 🙏

[smokyabdulrahman]

Any update on this issue is much appreciated.