Request/Response and messaging in same service; how do we filter?

[robbiewareham]

I am using PactNet 5.0.1 and I have a service that provides the following:

• POST request is made to my service which results in a message being written to a 3rd party queue.

I now have two pact files hosted in PactBroker; one generated by the consumer of the POST endpoint, the other generated by the process that reads the messages from the queue.

I've implemented the verification by having 2 classes, each with one Xunit test.

One class uses MessagingProvider and is configured to download from a pact broker:

 using var verifier = new PactVerifier(config);
   
 verifier.MessagingProvider("personal-details-api", CreateJsonSettings())
         .WithProviderMessages(scenarios =>
         {
             scenarios.Add("An event is created", _event);
         })
         .WithPactBrokerSource(_pactBrokerUri)
         .Verify();
 }

I was hoping/assuming that this would only download the messaging pact from pact broker but it is also downloading the request/response pact too so fails as it only expects messages.

The "provider" name in Pact Broker is the same (which makes sense to me as the provider is the same), but do I have to have unique provider names?

[YOU54F]

hey in pact v3 spec message and http pacts cannot be combined in a single pact file. v4 has this support.

due to this limitation for pact v3 users, the workaround is to name the message provider with some kind of differentiator from that from that of the http provider name.

moving to v4 pact spec should mitigate this requirement and would be the preferred path forward at this time

hope that helps