#bioworkflows
crude blaze
small steeple
Hi 👋 no, there is not a way to disable the generation of events. The only option that comes to mind is to shut down the listeners so they don't forward the events to your servers.
low ivy
But what bothers us was that even a "fresh" cli listener would get a lot of events from "old" tests that were completed by other test runs done a few days ago.
Should we try to use a different test key for each test run?
I think right now all tests receive the same "webhook signing secret" (whsec ...) so they share the same events.
small steeple
If you want to isolate tests from events for other tests, then yes you would need to conduct those tests in different accounts. All events for an account are sent to all listeners listening for that type of event.
Alternatively, you could update your webhook handler to handle those events so that they don't continually get retried. You can use metadata on your objects to indicate various tests, or use a single metadata parameter to indicate that events for the object should be ignored. Then your webhook handling code could check for that parameter to see if it should ignore the event, and if so still return a 2XX status back so the event isn't queued to be resent.
low ivy
Actually I receive the same whsec_ secret when I used different api keys
$ docker-compose run stripe --api-key=rksk_test_AlmUhcoRXRLQgzIiWvFahsWv0044DpR73M listen
Ready! You are using Stripe API Version [2020-03-02]. Your webhook signing secret is whsec_aa095929ad1b8d9e1fa93c6ce74797faf04f599ecba4c4a2da79812e269ca3f0 (^C to quit)
$ docker-compose run stripe --api-key=rk_test_51GOawPDccGCU5vwkKoNymqzJwfqWLrlJSrcHFsyMuBHf8W9hEyNG4XCScLEUzxyd3ovt1AvDS24ZFKbX7saeuOXv00SZ9cyYWY listen
Ready! You are using Stripe API Version [2020-03-02]. Your webhook signing secret is whsec_aa095929ad1b8d9e1fa93c6ce74797faf04f599ecba4c4a2da79812e269ca3f0 (^C to quit)
small steeple
That is expected, it's based on account, and doesn't change frequently:
https://stripe.com/docs/cli/listen#:~:text=The webhook signing secret provided will not change between restarts to the listen command.
I would recommend rolling your restricted keys now that they've been shared publicly though.
low ivy
OK. I will try the metadata approach and ask the webhook handler to do not hit the database if if the event contain certain metadata.
Thank you for your time. At least it help us confirm what actually was going on.
small steeple
Any time, happy to help!