In this context, webhooks are about ensuring there are no verification gaps or accelerating feedback loops.

can-i-deploy

prevents you deploying something that is unsafe (guards against various scenarios, including gaps in the test “matrix”, race conditions)

thanks for the answer! So, the last webhook arrow in the image is meant to accelerate the feedback loop, right? But it will trigger multiple consumer CI workflows for each provider verification (by "workflow," I mean a GitHub Actions). Does

can-i-deploy

keep polling the Pact Broker until all verification workflows are done or the max attempts are reached? Or does it stop polling when the first verification workflow ends?

can-i-deploy

is independent of the webhook. It will poll until the command passes with an exit status of

0

OR the timeout is reached (i.e. your polling settings)

I know that

can-i-deploy

is independent of the webhook. So, the answer to my question is yes: it will keep polling until all the verifications needed are completed OR the timeout is reached. Otherwise, it won’t return 0 and will continue polling. Thanks!