Problem
I have a complex setup that makes testing with the CLI a challenge because of some limitations with the stripe CLI.
I am receiving multiple different webhook endpoint hits to a listener which will dynamically discover the webhook secret based upon the endpoint signature and then proceed accordingly.
This works fine, the problem is local testing with the Stripe CLI.
My assumption was that -load-from-webhooks-api would sign the events with the proper webhook secret of the Webhook Endpoint the originated from. This is not the case. The cli uses the single generated webhook secret to sign them all. This makes testing my dynamic routine very hard.
Feature
I suggest a new flag of sorts: --sign-with-originating-webhook
This will sign with the originating endpoint.
Problem
I have a complex setup that makes testing with the CLI a challenge because of some limitations with the stripe CLI.
I am receiving multiple different webhook endpoint hits to a listener which will dynamically discover the webhook secret based upon the endpoint signature and then proceed accordingly.
This works fine, the problem is local testing with the Stripe CLI.
My assumption was that -load-from-webhooks-api would sign the events with the proper webhook secret of the Webhook Endpoint the originated from. This is not the case. The cli uses the single generated webhook secret to sign them all. This makes testing my dynamic routine very hard.
Feature
I suggest a new flag of sorts: --sign-with-originating-webhook
This will sign with the originating endpoint.