Another quick question regarding to

contract_requiring_verification_published

webhook event. In my provider's main pipeline I used tags to pull contracts like

-Ppactbroker.tags='master, dev, prod'

, since I changed to

contract_requiring_verification_published

, do I still have to use same approach to pull contracts? What is the recommended approach?

You would pass the pact URL to the webhook and read the URL in your build and then pass the URL to pact. See here: https://docs.pact.io/pact_broker/webhooks#template-parameters

You still use webhooks because these are used to verify new consumer contracts proactively. But when your provider code changes you still need to make sure they don't break existing consumers. In this case, your main build should continue to use tags (or environments/branches/releases as appropriate)

See this page on the steps to creating an effective contract-testing setup https://docs.pact.io/pact_nirvana. (This workshop demonstrates those principles in action: https://docs.pactflow.io/docs/workshops/ci-cd/)

Thanks that helped me a lot

@Shan you need to use branches and environments with the

contract_requiring_verification_published

event. You can’t use tags.