Hi there, I need some more clarification about

contract_requiring_verification_published

event. The doc, stated that "A webhook using the

contract_requiring_verification_published

should be configured to pass through the

${pactbroker.pactUrl}

and

${pactbroker.providerVersionNumber}

and

${pactbroker.providerVersionBranch}

to the provider verification build." I assume we need to pass version number (assume it is git SHA) so that we can checkout that GIT version before verifying the pact My questions is why do we need to pass

pactUrl

and

providerVersionBranch

& and how that can be useful?

The

pactUrl

is the thing that is being verified. It’s the pact that needs to be verified

Some ci systems want the branch to be supplied when you trigger a build.

@Matt (pactflow.io / pact-js / pact-go) So instead of

consumerVersionTags

, we should use

pactUrl

to get the correct contract from

pact broker

right?

Only for the webhook, yes

Great 👍. So what about the main build pipeline? Keep using consumerVersionTags?

If the provider versions that need to be verified are all different then yes, if they are the same then it will de-duplicate them