Example .NET Consumer - Pact-Net

Make sure you have set all of the environment variables, in powershell they can be set like so.

 $env:GIT_BRANCH="main"

Generate the Pact file for the example by opening the solution and running the tests in visual studio or using dotnet test CLI command in the root directory of the project.

Publish the pact that was generated. The step uses the pact-cli docker image to publish the pact to your pactflow account. The path for <path_to_project_root> needs to be converted from Windows paths to UNIX ones as the Docker container is using UNIX. Either hard code this or set it as another environment variable.

`C:\Users\Person\Documents\example-bi-directional-consumer-dotnet` 

becomes

`/c/Users/Candy/Documents/API Hub for Contract Testing/example-bi-directional-consumer-dotnet`

$env:VARIABLE_NAME refers to the environment variables in windows.

```
docker run --rm -v <path_to_project_root>:<path_to_project_root> -e PACT_BROKER_BASE_URL -e PACT_BROKER_TOKEN pactfoundation/pact-cli publish <path_to_pacts_folder> --consumer-app-version $env:GIT_COMMIT --branch $env:GIT_BRANCH

```

Check can-i-deploy to see if your provider is compatible with your pact.

docker run --rm -v <path_to_project_root>:<path_to_project_root> -e PACT_BROKER_BASE_URL -e PACT_BROKER_TOKEN pactfoundation/pact-cli  broker can-i-deploy --pacticipant pactflow-example-bi-directional-consumer-dotnet --version $env:GIT_COMMIT --to-environment production  --retry-while-unknown 0 --retry-interval 10

Have a look at what other commands are available in the Makefile. All of them can be ran locally from Powershell by changing the windows paths to UNIX and replacing the environment variable references. Any variable referenced as ${VARIABLE} can be changed to $env:VARIABLE to reference environment variables in Powershell.