This tool provides an amalgamated CLI of all the Pact CLI tools available in the Pact Ruby implementation (to interact with the Pact Broker, publish and verify pacts) & the new Pact-Rust implementation (to run a mock or stub server, verify pact). While it is functionally the same as the pact-ruby-standalone plus the individual component rust CLI's it is packaged as a Docker container and a single top level entrypoint (pact).
Multi-platform images are available, and can be used cross-platform by setting the platform flag.
-
--platform=linux/amd64 -
--platform=linux/arm64docker run --rm -it pactfoundation/pact-cli:latest /bin/sh -c 'uname -sm'
You can run the following examples against a public test Pact Broker with the following credentials:
export PACT_BROKER_BASE_URL="https://test.pactflow.io"
export PACT_BROKER_USERNAME="dXfltyFMgNOFZAxr8io9wJ37iUpY42M"
export PACT_BROKER_PASSWORD="O5AIZWxelWbLvqMd8PkAVycBJh2Psyg1"
The $(date +%s) in the examples is just to generate a pseudo random GIT_COMMIT.
If you are using a Pact Broker with bearer token authentication (eg. PactFlow), then set PACT_BROKER_TOKEN instead of the username and password.
- If you are publishing pacts, don't forget to mount your pacts into the docker container using the
-vflag, documented in the example below. - If you are connecting to a Pact Broker that you are running on
localhost, you will need to add--network="host"to the docker command so that it resolveslocalhostto your machine, rather than to the container itself.
$ docker run --rm docker.swagger.io/pactfoundation/pact-cli:latest help
Commands:
help [COMMAND] # Describe available commands or one specific command
mock-server # Run a Pact mock server
mock-service # (legacy) Run a Pact mock service
pact-broker # Interact with a Pact Broker (also aliased as the subcommand `broker`)
pactflow # Interact with PactFlow
plugin # Run the Pact plugin cli
publish PACT_DIRS_OR_FILES ... # Publish pacts to a Pact Broker.
stub-server # Run a Pact stub server
stub-service # (legacy) Run a Pact stub service
verifier # Run a Pact verifier
verify PACT_URL ... # (legacy) Verify pact(s) against a provider. Supports local and networked (http-based) files.
version # Print the version of the CLI
$ docker run --rm docker.swagger.io/pactfoundation/pact-cli:latest pact-broker help
Commands:
pact-broker can-i-deploy -a, --pacticipant=PACTICIPANT -b, --broker-base-url=BRO...
pact-broker create-version-tag -a, --pacticipant=PACTICIPANT -b, --broker-base-u...
pact-broker create-webhook URL -X, --request=REQUEST -b, --broker-base-url=BROKE...
pact-broker describe-version -a, --pacticipant=PACTICIPANT -b, --broker-base-url...
pact-broker help [COMMAND] ...
pact-broker publish PACT_DIRS_OR_FILES ... -a, --consumer-app-version=CONSUMER_A...
pact-broker version ...
You can clone git@github.com:pact-foundation/pact-ruby-cli.git (https://github.com/pact-foundation/pact-ruby-cli) and run the following from the root directory.
docker run --rm \
-w ${PWD} \
-v ${PWD}:${PWD} \
-e PACT_BROKER_BASE_URL \
-e PACT_BROKER_USERNAME \
-e PACT_BROKER_PASSWORD \
pactfoundation/pact-cli:latest \
publish \
${PWD}/example/pacts \
--consumer-app-version fake-git-sha-for-demo-$(date +%s) \
--tag-with-git-branch
See https://github.com/pact-foundation/pact_broker-client#publish for all publish options.
docker run --rm \
-e PACT_BROKER_BASE_URL \
-e PACT_BROKER_USERNAME \
-e PACT_BROKER_PASSWORD \
pactfoundation/pact-cli:latest \
publish \
/pact/example/pacts \
--consumer-app-version fake-git-sha-for-demo-$(date +%s)
See the example docker-compose-verify.yml
PACT_BROKER_PUBLISH_VERIFICATION_RESULTS=true GIT_COMMIT=fake-git-sha-for-demo$(date +%s) GIT_BRANCH=master \
docker-compose -f docker-compose-verify.yml \
up --build --abort-on-container-exit --exit-code-from pact_verifier
For the verifier, please see https://github.com/pact-foundation/pact-reference/tree/master/rust/pact_verifier_cli#command-line-interface for all verification options.
See docker-compose-verify-legacy.yml for the legacy Pact-Ruby based implementation.
For the legacy verifier, please see https://github.com/pact-foundation/pact-provider-verifier/#usage for all verification options.
docker run --rm \
-e PACT_BROKER_BASE_URL \
-e PACT_BROKER_USERNAME \
-e PACT_BROKER_PASSWORD \
pactfoundation/pact-cli:latest \
pact-broker can-i-deploy \
--pacticipant docker-example-consumer \
--latest
See https://github.com/pact-foundation/pact_broker-client#can-i-deploy for all options.
docker run --rm \
-e PACT_BROKER_BASE_URL \
-e PACT_BROKER_USERNAME \
-e PACT_BROKER_PASSWORD \
pactfoundation/pact-cli:latest \
pact-broker create-version-tag \
--pacticipant docker-example-consumer \
--version fake-git-sha-for-demo-$(date +%s) \
--tag prod
See https://github.com/pact-foundation/pact_broker-client#create-version-tag for all options.
docker run -dit \
--rm \
--name pact-mock-server \
-p 8080:8080 -p 9000-9020 \
-v ${HOST_PACT_DIRECTORY}:/tmp/pacts \
pactfoundation/pact-cli:latest \
pact_mock_server_cli start \
--base-port 9000
The -it is required if you want the container to respond to a ctl+c. The container takes an unexpectedly long time to shut down when using docker stop. This is an open issue.
See https://github.com/pact-foundation/pact-core-mock-server/tree/v1.0.x/pact_mock_server_cli#command-line-interface for all options.
docker run --rm -it \
-p 8080:8080 \
pactfoundation/pact-cli:latest \
stub-server \
--dir /pact/example/pacts \
--port 8080
Provides a stub server that can generate responses based on pact files. See https://github.com/pact-foundation/pact-stub-server?tab=readme-ov-file#command-line-interface for all options
Legacy ruby mock-service, replaced by mock-server command implemented in Rust.
docker run -dit \
--rm \
--name pact-mock-service \
-p 1234:1234 \
-v ${HOST_PACT_DIRECTORY}:/tmp/pacts \
pactfoundation/pact-cli:latest \
mock-service \
-p 1234 \
--host 0.0.0.0 \
--pact-dir /tmp/pacts
The -it is required if you want the container to respond to a ctl+c. The container takes an unexpectedly long time to shut down when using docker stop. This is an open issue.
See https://github.com/pact-foundation/pact-mock_service#mock-service-usage for all options.
The Pactflow AI tool is included in the image for convenience, for more commands refer to the documentation and find example usage below:-
docker run --rm \
pactfoundation/pact-cli:latest \
--mount type=volume,source=<volume-name>,target=<mount-path-in-container> \
-e PACT_BROKER_BASE_URL="https://YOUR_ORG.pactflow.io" \
-e PACT_BROKER_TOKEN="YOUR_TOKEN" \
pactflow-ai --help
Demo
- Set
PACT_BROKER_BASE_URL/PACT_BROKER_TOKENin shell, before running below command - Create a folder called
outputin the current directory.
docker run --rm \
-v $PWD/output:/output \
-e PACT_BROKER_BASE_URL \
-e PACT_BROKER_TOKEN \
pactfoundation/pact-cli:latest \
pactflow-ai \
generate \
--openapi /pact/example/provider-contracts/oas.yml \
--endpoint "/admin/teams/{uuid}" \
--output /output/api.pact.spec.ts \
--language typescript
docker run --rm \
-v <PATH_TO_CERT_FILE_ON_HOST>:/tmp/cacert.pem \
-e SSL_CERT_FILE=/tmp/cacert.pem \
pactfoundation/pact-cli:latest ...
You can also set SSL_CERT_DIR and mount the directory instead of the file.
To connect to a Pact Broker that uses x509 certificates for client authentication:
docker run --rm \
-v <PATH_TO_CLIENT_CERT_FILE_ON_HOST>:/tmp/clientcert.pem \
-v <PATH_TO_CLIENT_KEY_FILE_ON_HOST>:/tmp/clientkey.pem \
-e X509_CLIENT_CERT_FILE=/tmp/clientcert.pem \
-e X509_CLIENT_KEY_FILE=/tmp/clientkey.pem \
pactfoundation/pact-cli:latest ...
To meet with Docker consistency rules sh access is provided, NOTE: bash is not installed in the container
$ docker run --rm docker.swagger.io/pactfoundation/pact-cli sh -c 'ls'
Gemfile
Gemfile.lock
bin
entrypoint.sh
example
lib
pact-cli.gemspec
$ docker run --rm docker.swagger.io/pactfoundation/pact-cli ls
Gemfile
Gemfile.lock
bin
entrypoint.sh
example
lib
pact-cli.gemspec
Bug reports and pull requests are welcome on GitHub at https://github.com/pact-foundation/pact-ruby-cli.
The gem is available as open source under the terms of the MIT License.
pactfoundation/pact-broker uses Scarf to collect anonymized download analytics. These analytics help support the maintainers of this image and ONLY run when you pull the image through the Scarf gateway (the pull commands shown throughout this README). To opt out, pull the image directly from Docker Hub:
docker pull pactfoundation/pact-brokerAlternatively, block static.scarf.sh at the network level (or disable image loading in your browser when viewing this README) to disable the README impression pixel.
For more information, see docs.pact.io/telemetry.
