I'm trying to use the dockerized Pact Broker CLI for my POC and I'm trying to figure out what is supported by the Pact Broker Client and what isn't my use case: I am using the REST interface: for (1)

<http://localhost:8500/pacts/provider/inventory_provider/latest>

to see which are the latest pacts targeting my provider

inventory_provider

this gives me the list of the latest versions of consumers so I picked one of them and called: (2)

localhost:8500/pacts/provider/inventory_provider/consumer/inventory_consumer1/version/1.1.2

which gives the pacts for

inventory_provider

defined by

inventory_consumer1

of version

1.1.2

- this gives me the actual pact the Pact Broker Client documentation lists only the more "procedural" operations of pushing pacs, managing environments and deployments etc. but is there a Pact CLI command that allows me to perform operations such as (1) and (2) or are these only supported via the REST interface?

Yeah I don’t think those are commonly use operations, so presumably that’s why they aren’t there. You could always submit a PR to that project to add them, but first - what’s the use case you’re trying to establish here?

I'm working with a very large application running as a

@SpringBootTest

- takes several minutes to spin up and state setup calls may take a long time so over all long execution time I want to see if I would be able manage the downloading of the pacts from Pact Broker myself and basically replace

@PactBroker

with

@PactFolder

and potentially even spread the pacts across multiple instances/invocations of the test class so it could be run in parallel on multiple machines in parallel