Hi all, I have a question about next steps list provided by pact-broker publish command: View the published pact at https://xxx.pactflow.io/pacts/provider/provider-app/consumer/consumer-app/version/xxx Events detected: contract_published, contract_requiring_verification_published Next steps: * Add Pact verification tests to the provider-app build. See https://docs.pact.io/go/provider_verification * Configure separate provider-app pact verification build and webhook to trigger it when the pact content changes. See https://docs.pact.io/go/webhooks Why are the next steps needed? Are they required for the ci/cd to work correctly?

with all due respect read the links provided to understand more

I have red them but they are a bit confusing and I asked here for having an answer from an expert, that could make things a bit more clear to me. What I understand from the docs is that we need to extract a provider verification build to a post endpoint, and create a webhook to use that endpoint and be triggered on contract_requiring_verification_published event. That will try to verify provider for published changed consumer contracts. Is that right, and have I missed anything here?

you need two provider builds https://docs.pact.io/pact_nirvana/step_4#verifying-pacts one is ideally triggered by a webhook so it can be orchaestrated by the broker, whenever a pact changes and can trigger versions of your provider code depending on which versions of your provider are deployed or released as well as on the main branch which makes sure your newly created unverified pact gets validated against all the relevant providers