Hey 👋🏻 Unfortunately I did not found any information about my current problem. So we have successfully integrated PACT between two (asynchronous) services. Basically all the pieces are tight together, last part I was working on was integrating web hooks whenever a contract changed that

required

verification. To come to the question: We saw that PACT verified several versions - especially from PR's which actually might not exist anymore at this time. I think it would make most sense to just verify against deployed versions of a service right? Basically latest master/main would be fine + all versions deployed on environments (recorded deployments). Is there some configuration available? Here is my current (provider) test setup

@Provider("goto-conference-service")
@PactBroker
@SpringBootTest
@Import(KafkaConsumerConfiguration.class)
@AutoConfigureMockMvc
@AllowOverridePactUrl
public class ConferenceEventsContractTests extends TestcontainersIntegrationTests {

    @Autowired
    private MockMvc mockMvc;

    @Autowired
    private ObjectMapper objectMapper;

    @TestTemplate
    @ExtendWith(PactVerificationInvocationContextProvider.class)
    void testTemplate(Pact pact, Interaction interaction, PactVerificationContext context) {
        context.verifyInteraction();
    }

    @BeforeAll
    static void beforeAll(){
        PactBrokerDefaults.initFallbackTokenIfMissing();
        PactBrokerDefaults.initFallbackUrlIfMissing();
    }

    @BeforeEach
    void before(PactVerificationContext context) {
        context.setTarget(new MessageTestTarget());
    }

    @PactVerifyProvider("valid conference created event")
    public String verifyConferenceCreatedEvent() throws Exception {
        ConferenceEvent createdEvent = getEventByCreateTrigger(event -> "ConferenceCreated".equals(event.getEventName()));
        return objectMapper.writeValueAsString(createdEvent);
    }
    
    // some more not relevant pieces of code
}

I think you may have forgotten to make use of

consumerVersionSelectors

property of the PactBroker annotation. You basically skipped the "Gold" step of Pact Nirvana I think: https://docs.pact.io/pact_nirvana/step_5 Without the consumerVersionSelector, your provider verifies all latest PACTs it finds

I didnt know about the pact nirvana let me check that, thanks. To your suggestion - yes I'm doing that and that got me confused as well. Here is my pipeline step

stage('verify') {
            steps {
                script {
                    def config = readYaml file: 'pact.yaml'
                    def verificationCommand = config.VERIFICATION_COMMAND
                    if (!verificationCommand?.trim()) {
                        error("Please configure a pact 'VERIFICATION_COMMAND'")
                    }
                    verificationCommand = verificationCommand + " -Dpact.filter.consumers=${consumer} -Dpact.filter.pacturl=${pactUrl}"
                    echo "pact provider verification command = ${verificationCommand}"
                    mavenBuilder 'test', customParams: verificationCommand
                }
            }
        }

Do you find the PACT URL appears in the maven build logs?

Looks like that when pactflow triggered my jenkins job it seams I got all the required data

pact provider verification command = -Dtest=ConferenceEventsContractTests -Dpact.filter.consumers=goto-provisioning-service -Dpact.filter.pacturl=<https://xxx.pactflow.io/pacts/provider/goto-conference-service/consumer/goto-provisioning-service/pact-version/865103be9f0e9eedd7b29ccdf8339e2d4f0e7458/metadata/Y3ZuPTEuMS4yLVBSLTI4NC1iNWM0MjdmJnc9dHJ1ZQ>

So far so good. And if you turn on DEBUG logging of

org.apache.hc

you should see outgoing traffic to that URL, do you?

that will take some time to test that