#KrisMatrix
1 messages · Page 1 of 1 (latest)
hello! can you try using the override flag and see if that works? https://stripe.com/docs/cli/trigger#trigger-override
e.g.
stripe trigger charge.failed --override charge:customer=cus_456--override charge:source=card_123
hmm...It does not appaer to.
can you share the command you tried?
Don't understand what [resource]:[path1].[path2] is
hold on. I will do that.
/stripe trigger checkout.session.completed
and followed by:
./stripe trigger invoice.paid --override charge:customer=cus_MsixujmoNp4IJD
gimme a while to check
Would it also help for me to share the node code for stripe_webhook?
nah, i don't need the webhook code at the moment. will let you know if i need it later!
sure
hmmm, i can't get invoice.paid to work with override. I think your only option would be to write your own fixture file - https://stripe.com/docs/cli/fixtures
you can take a look at the example fixtures here that we're using for the triggers : https://github.com/stripe/stripe-cli/tree/master/pkg/fixtures/triggers
Thank you. I probably need to spare some time to look into this. It sounds like I can somehow chain things for the purpose of simulation/testing?
yep, if you look at the example fixture for invoice.paid for example - you'll see that it calls a series of requests (chaining) - https://github.com/stripe/stripe-cli/blob/master/pkg/fixtures/triggers/invoice.paid
thank you for now.