3 ms·
> We built against Stripe's sandbox and never had to test in production, so I never had to use a real credit card. Did it, got bit in the ass when some workflo
by arkh 2y ago
> We built against Stripe's sandbox and never had to test in production, so I never had to use a real credit card.
Did it, got bit in the ass when some workflow was disabled in production and not in their sandbox. I don't recall the exact thing but always fun to push into production all sure of yourself to have to rollback fast and ponder why you get some fun message in your logs. At least the error message was clear about what we were doing being available only on the sandbox.
It was some years ago so I don't remember if it was in Stripe Connect or during the mandatory 2FA rollout.
- ambicapter 2y ago> got bit in the ass when some workflow was disabled in production and not in their sandbox What Stripe workflow was this? Or was it specific to your codebase?
- danielheath 2y agoStripe is the best I've used, but it has a ton of issues to this day: A) Account settings are specified separately in prod / staging B) Differences between those environments are not automatically reported in a useful way C) Only one staging env per customer. Want to check what a new setting will do? Every developer is getting that setting turned on.
- dmlittle 2y ago> C) Only one staging env per customer. Want to check what a new setting will do? Every developer is getting that setting turned on. Stripe Sandboxes[1] aim to solve this problem! (Disclaimer: I work for Stripe but not on this feature) [1] https://docs.stripe.com/sandboxes https://docs.stripe.com/sandboxes
- danielheath 2y ago"up to six" is definitely an improvement, but still a long way from "ephemeral test environments on demand".