pact

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "env

When Pact fails, it's a bit hard to know what the issue is considering the requests are not being printed back to the terminal. At the moment, I'm using this custom method to do this but I think it would be nice to have something like this out of the box.

public static void logCurlFromPact(PactVerificationContext context, HttpRequest request) {

        String bodyParam = ((RequestRespon

Version 1.6.7 has two CVEs related to the dependencies github.com/gin-gonic/gin v1.7.2 (vulnerability) and gopkg.in/yaml.v2 v2.2.2 (vulnerability) that could be fixed by bumping the dependencies to the latest version.

Hi, I'd like to implement the flow where verification is triggered via webhook. One can configure various options (ncluding authorization token) for WithPactBrokerSource, however for WithUriSource there's no such possibility. How can I pass auth token when using uri source?

enforce is currently strict in the error message, which means that e.g. using format to make an informative error is expensive even if the test passes.

The fastapi example (and perhaps the others) are a little misleading to newbies.

The following lines would suggest that there is pact mock on the provider side, when in reality this is the address of the locally running FastAPI provider:

PACT_MOCK_HOST = 'loca

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

-Dpact.rootDir="target/pact-classes" didn’t work for me.
env "pact.rootDir=target/pact-classes" bash did

...because of the "."

If no interaction with the path matches -> 404
If an interaction with the path matches but the headers/request is wrong -> 400/405 or 415

@uglyog if you can point to a test that shows how the rust one does it, it would be good to make them the same.