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
Stripe allows production environment to use different URLs for each event (for example /stripe/webhook/coupon/created for coupon.created and so on). This is great because it's best practice to avoid having a switch of death on one single route that will dispatch all events.
As of today, it seems this cannot be done using the Stripe CLI without having to start as many commands as there are events to listen to. Obviously when working with a fully automated local environment using Docker it is not viable to start as many Stripe CLI containers as there are events type to listen to.
Feature
It would be good to be able to specify which event to route where when using the Stripe CLI. Ideally this would be done using the configuration file to avoid having a super long (and possibly confusing) command line.
Problem
Stripe allows production environment to use different URLs for each event (for example /stripe/webhook/coupon/created for coupon.created and so on). This is great because it's best practice to avoid having a switch of death on one single route that will dispatch all events.
As of today, it seems this cannot be done using the Stripe CLI without having to start as many commands as there are events to listen to. Obviously when working with a fully automated local environment using Docker it is not viable to start as many Stripe CLI containers as there are events type to listen to.
Feature
It would be good to be able to specify which event to route where when using the Stripe CLI. Ideally this would be done using the configuration file to avoid having a super long (and possibly confusing) command line.
Examples
Let's have some
toml
example:The text was updated successfully, but these errors were encountered: