Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specifying different endpoints for each event for the listen command. #1133

Open
SmashingQuasar opened this issue Nov 14, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@SmashingQuasar
Copy link

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:

[webhooks]
coupon.created = 'https://my.local.environment.dev/stripe/webhook/coupon/created'
@SmashingQuasar SmashingQuasar added the enhancement New feature or request label Nov 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant