From fbaa9259e1e9be040c06b4db7f8e3171cec61e07 Mon Sep 17 00:00:00 2001 From: Github Action Date: Mon, 8 Jul 2024 06:32:29 +0000 Subject: [PATCH] chore: synced pact-rust docs --- .../implementation_guides/rust/pact_verifier_cli.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/website/docs/implementation_guides/rust/pact_verifier_cli.md b/website/docs/implementation_guides/rust/pact_verifier_cli.md index b3aa169b..4e02ca09 100644 --- a/website/docs/implementation_guides/rust/pact_verifier_cli.md +++ b/website/docs/implementation_guides/rust/pact_verifier_cli.md @@ -367,7 +367,9 @@ This is supported on Windows, macOS and Linux: On Linux the standard OpenSSL environment variables `SSL_CERT_FILE` and `SSL_CERT_DIR` will also be respected. -## Verifying V4 Pact files that require plugins +## Verifying V4 Pact files + +### Pact files that require plugins Pact files that require plugins can be verified with version 0.9.0-beta.0+. For details on how plugins work, see the [Pact plugin project](https://github.com/pact-foundation/pact-plugins). @@ -378,3 +380,11 @@ variable. Each plugin required by the Pact file must be installed there. You wil instructions for each plugin, but the default is to unpack the plugin into a sub-directory `-` (i.e., for the Protobuf plugin 0.0.0 it will be `protobuf-0.0.0`). The plugin manifest file must be present for the plugin to be able to be loaded. + +### Verifying both HTTP and message interactions + +V4 Pact files can support both HTTP and message-based interactions in the same file. In this case, the be able to +handle the verification for both types of interactions you need to use the `--transports ` option. This will +allow configuring different ports to send the different requests to. + +For example, `--transports http:8080 message:8081` will send HTTP requests to port 8080 and message requests to port 8081.