For now, if there is multiple matching interactions, the mock service return only one response.
From doc:
Where multiple matching interactions are found, the interactions will be sorted by response status, and the first one will be returned. This may lead to some non-deterministic behaviour.
To stay in line with the Pact philosophy and pact description, why not just introducing a custom HTTP header "X-Provider-State" to let the consumer set the expected provider state.
Like this, the mock service can know the response to produce based on the pact.
Hi,
For now, if there is multiple matching interactions, the mock service return only one response.
From doc:
Where multiple matching interactions are found, the interactions will be sorted by response status, and the first one will be returned. This may lead to some non-deterministic behaviour.
To stay in line with the Pact philosophy and pact description, why not just introducing a custom HTTP header "X-Provider-State" to let the consumer set the expected provider state.
Like this, the mock service can know the response to produce based on the pact.
Regards
Thank you