Hi everyone! I'm not sure if this is the channel to ask this question, but here we go. I'm trying to use providers states to create an entity and then test the contract of a

get

endpoint for that entity. I need to create it first so that the endpoint doesn't return a 404. I have created a provider state setup function in my API, that creates this entity and returns a dictionary with the relevant value for the generator. I am using the docker pact-cli for verifying the provider, and it is calling that endpoint correctly. My issue is that it is not modifying the pact to use the returned id instead of the example specified in the pact. Here's an example of my code:

// Consumer in JavaScript
provider
      .given("an existing experiment")
      .uponReceiving("a request to get the experiment")
      .withRequest({
        method: "GET",
        path: fromProviderState("/v3/experiments/${uuid}", `/v3/experiments/${exampleUuid}`),
      })
      .willRespondWith({
        status: 200,
        body: { resource: like({
                 uuid: fromProviderState("${uuid}, exampleUuid)
              })},
      }));

# Provider state setup endpoint (Python & FastApi)
@router.get(/pact/setup)
def pact_setup():
    experiment = create_experiment()
    return { "uuid": experiment.uuid }

The setup function is being called by the docker verifier, returning the uuid of the created experiment, but the provider verification is still executing a get request to the

exampleUuid

. Is there anything I'm missing?

Can you show us the verifier configuration?

Python doesn’t support verifying V3 pacts, and doesn’t understand the “from provider state” feature

ah, of course

Oooh. I see. I'm not using pact-python though. Verification is being done through the pact cli docker image. Doesn't that support provider injection? It is calling the setup function correctly (requests are logged properly). It's just not injecting the return value on the contract.

Aha!

Well, that explains a lot 😅. I knew it used the ruby version, but I didn't know it doesn't support provider state injection. Thank you for the help and support!

No worries, it’s confusing. I’m sorry about that

That would be great! I ended up making my verifier in JS, but it would be nice to have a cli ready to use.