Hello, we have successfully added the `contract_re...
# general
t
Hello, we have successfully added the
contract_requiring_verification_published
webhook, but I am now wondering if we need to add a webhook to trigger consumer build when provider verification is published or not, I see it in the diagram but its not clear if I actually need it or not, as once I add
can-i-deploy
I can use the
--retry-while-unknown
parameter? Or am I missing something obvious here? Thanks
m
WOOT!
I’d hold off adding that webhook until you have a need, personally
t
ok thanks so i guess i should do
can-i-deploy
as next step in my pact journey then?
💯 1
what is normally the need for that webhook?
m
what is normally the need for that webhook? (edited)
There are probably some use cases that are now no longer required because of newer functionality (e.g. pending, wip etc.). In most cases, there shouldn’t be any “gaps” with what’s described in the Nirvana guide/workshop
t
ok thanks 🙂
👍 1
y
Running cid with retry is good. You publish your pact, if it needs verification, an event is emitted and a webhook kicks off the provider build for a contract requiring validation ( by pact url ) this reports a successful verification Consumer can I deploy will return a result after the provider has performed their verifications based on the builds The retry mechanism is nice here as the consumer can deploy straight after all the necessary verifications are complete. The diagrams and flow on the path to nirvana need updating at the moment to reflect the new ci/cd workshop. I think there will be less steps, and as it will no longer be using tags, both for environments and branches, and uses the new webhook which ensures changed pacts are verified on the latest of the main branch, and any deployed or released versions There are alternative means. The consumer for whatever reason may mechanisms and purposes for webhooks. A provider verification successful result, you may want to report back in a GitHub pull request status check, or trigger the consumers build to run. If you can provide a diagram of your pipeline setup we can help advise on or discuss a suitable workflow.
t
Yep thanks the retry mechanism in can-I-deploy works well but have another question now that I posted separately :)