Ensure PACT_DESCRIPTION and PACT_PROVIDER_STATE env vars can be passed down to pact verify to allow selected interactions to be run about pact-go HOT 11 CLOSED

@bethesque from the provider side, how would we determine which provider description/state to tell the user? It's quite a blunt instrument at the moment as we get back only unstructured data from a single call to 'verify'.

I see a few options here:

1. Have the verifier (and mock service?) send back structured data that the client libraries can use more intelligently (this might be required for other scenarios, such as message/other engine support)
2. Have the verifier output a generic message as per your suggestion that doesn't
3. Have a clear message in the unstructured data that can be filtered and used to make this decision
4. Be quite generic and just tell the user they can do this sort of thing
5. Something else I can't imagine at this moment in time

from pact-go.

FWIW it's worth, it works for Pact Go:

PACT_DESCRIPTION="yeah" PACT_PROVIDER_STATE="blah" make pact
...
Reading pact at /Users/mfellows/go/src/github.com/pact-foundation/pact-go/examples/e2e/../pacts/billy-bobby.json
Filtering interactions by: {:description=>/yeah/, :provider_state=>/blah/}
No examples found.

0 interactions, 0 failures

from pact-go.

For each failure in the pact, the ruby code outputs the command to run that individual interaction (you probably just gloss over that as it's not relevant for js/go).

Failed interactions:

bundle exec rake pact:verify:at[./spec/support/test_app_fail.json] PACT_DESCRIPTION="a test request" PACT_PROVIDER_STATE="the weather is cloudy" # A test request given the weather is cloudy
bundle exec rake pact:verify:at[./spec/support/test_app_fail.json] PACT_DESCRIPTION="another test request" PACT_PROVIDER_STATE="" # Another test request
bundle exec rake pact:verify:at[./spec/support/test_app_fail.json] PACT_DESCRIPTION="another test request" PACT_PROVIDER_STATE="a missing provider state" # Another test request given a missing provider state

If the calling code can also set an environment variable called PACT_INTERACTION_RERUN_COMMAND then I can use that to create language specific re-run commands. Otherwise, I can just print the description/state env vars for each interaction, with the text "Please re-run the verify command with the relevant env vars set to run an individual interaction"

from pact-go.

The value of PACT_INTERACTION_RERUN_COMMAND for ruby is

bundle exec rake pact:verify:at[<PACT_URI>] PACT_DESCRIPTION=\"<PACT_DESCRIPTION>\" PACT_PROVIDER_STATE=\"<PACT_PROVIDER_STATE>\"

I substitute in the relevant description, state and URL.

from pact-go.

Yep, but it doesn't do that anymore right?

PACT_INTERACTION_RERUN_COMMAND seems like a good suggestion. Is that already available?

from pact-go.

I've already done it.

from pact-go.

I think that was a race condition - I can do that :)

from pact-go.

I've updated the code base to set PACT_INTERACTION_RERUN_COMMAND when running the verification process. Let us know when it's in the upstream package. I'm running it locally against 1.4.2 and it's still wanting to do Ruby stuff.

from pact-go.

Bother, I thought I had already. Will go and check my releases.

from pact-go.

It's working for me with 1.4.2. If I run

PACT_INTERACTION_RERUN_COMMAND="foo" ./pact-provider-verifier -a "1.0.100" --provider-base-url http://localhost:4567 --pact-urls fail.json --provider_states_setup_url http://localhost:4567/provider-state -v

I get:

3 interactions, 2 failures

Failed interactions:

foo # Greeting fail
foo # Provider state success

from pact-go.

I worked out why - we use the --json flag and it doesn't seem to come through in there (and for good reason).

I'll update docs and have the code pass it through anyway for future safe-keepings.

from pact-go.