#spoolyx
waxen viper
Hi there!
No there isn't. That's something that you'll need to do manually, either in the dashboard or with the API.
bitter dagger
I see, well, thanks anyway! 🙂
echo umbraBOT
twin bolt
@bitter dagger can you move your follow up question to this thread?
Since you already have a thread open
bitter dagger
Of course, sorry, I didn't know that was the correct action since they are unrelated questions!
I want to trigger a checkout.session.completed on my localhost for testing purposes using Stripe CLI, and it works fine if I do stripe trigger checkout.session.completed -- however, it creates a new product and price everytime I trigger this event. Is there a way to tell stripe-cli that they should use an existing product/price instead of creating a new one in every action? I want to mimic the exact order of events that I get as if the user checked out using the pricing table, which obviously doesn't involve creating a new product/price
twin bolt
I believe you can use a stripe CLI flag to override the parameters CLI uses when running the fixture, hold on. Let me see if there any docs around this.
The flag you'd use is --override
https://stripe.com/docs/cli/trigger#trigger-override
We don't have any examples of the flag being used though 😦
The other option would be for you to use a custom fixture instead which you can base off of the current checkout.session.completed fixture here
https://github.com/stripe/stripe-cli/blob/master/pkg/fixtures/triggers/checkout.session.completed.json
although going back to your original ask
I want to mimic the exact order of events that I get as if the user checked out using the pricing table, which obviously doesn't involve creating a new product/price
We don't recommend relying on the order of the events as they are supposed to be asynchronous. We never gurantee the order for any webhook events.