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
Have the CLI Reuse and Cleanup the test data it creates (i.e. clean up your own mess) #1092
Comments
Thanks for the suggestion! In the meantime, you can delete all test data on the account with a single click via the Dashboard. |
The problem I'm facing is that I have products in the test environment that I need to keep. Deleting the test data manually is at best tedious and at worst impossible. |
Yeah this is quite the disappointment. Deleting all your test data also deletes all the products etc. that you carefully crafted, not just the mock products created by the CLI. Found out the hard way... |
Doing a google search for If stripe-cli won't track and clean up the data it creates, we need some other options. Here are some suggestions.
|
I've stopped using trigger now. Instead I create the event by using the checkout, then I replay the events that created as needed. |
@hades200082 Cool, are you using the CLI to replay, or is that a dashboard-only function? |
I use the CLI to replay it. |
Problem
Use the Stripe CLI to build out integrations without interfering with other users creating test products that are effectively "drafts" waiting to move to production or getting in their way.
As it stands the Stripe CLI can create hundreds or thousands of products, customers, etc. in a single day of development and testing. It's unacceptable that this test data is left in my test account with no simple way to remove it without also removing the test data I created manually (i.e. the drafts of what will be my live plans/products eventually)
Feature
trigger
command.As I see it the stripe CLI is creating a mess in my test account. It's the CLIs responsibility to clean up after itself.
Also see:
The text was updated successfully, but these errors were encountered: