In preparation for updating these repos to PactNet 4.x
Will possibly create a spin off branch called 3.x for legacy reasons
Bonus points
Have also allowed for the provider side verification to take place
Locally via PACT_URL, but not passing in a token, (so that you can run both repos on the machine PACT_URL=/Users/saf/dev/DIUS/example-consumer-dotnet/pacts/pactflow-example-consumer-dotnet-pactflow-example-provider-dotnet.json make test without it bailing if you don't have env vars set
Use PACT_BROKER_TOKEN if set
otherwise see if PACT_BROKER_USERNAME is set and use that along with PACT_BROKER_PASSWORD or assume there are no credentials on the broker.
This allows you a user to
verify both applications cloned locally, without a broker
verify both applications with pacts pushed to an OSS Pact broker
verify both applications with pacts pushed to a PactFlow Broker
Updates to
In preparation for updating these repos to PactNet 4.x
Will possibly create a spin off branch called 3.x for legacy reasons
Bonus points
Have also allowed for the provider side verification to take place
PACT_URL
, but not passing in a token, (so that you can run both repos on the machinePACT_URL=/Users/saf/dev/DIUS/example-consumer-dotnet/pacts/pactflow-example-consumer-dotnet-pactflow-example-provider-dotnet.json make test
without it bailing if you don't have env vars setPACT_BROKER_TOKEN
if setPACT_BROKER_USERNAME
is set and use that along withPACT_BROKER_PASSWORD
or assume there are no credentials on the broker.This allows you a user to