Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

Future documentation for this feature:

To delete pacts for a specific tag.

• Open the Pact Broker and click "show latest tags"

• Scroll to the row for the consumer/tag that you wish to delete.

• Click on the "..." icon for that row

• Select "Delete pacts for tag <tag>"

• You will see a prompt with the text

  This will delete the pacts for provider <provider> and all ver
  

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

These keys can be used in various combinations ( eg. { "environment": "prod", released: true, consumer: "Foo" } ). Please allow any combination

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

Is your feature request related to a problem? Please describe.
I want to use external JSON schema provided in @exodus/schemasafe

Describe the solution you'd like
Please add an optional argument for external schemas to expectJsonSchema and jsonSchema methods.

Describe alternatives you've considered
Or maybe

Description
When the file passed to the stub does not exist, the stub neither displays an error nor exits.

Steps to reproduce

1. Run the command qontract stub nonexistent.qontract
2. Qontract runs, but prints nothing, nor does it exit.

Expected behavior
If any of the files or directories provided do not exist, Qontract should highlight this, but it should not die if there is

❕ Problem Statement

Provide resources to help new users become proficient in Pact and PactSwift

💬 Task Description

Create an end-to-end workshop based on the canonical pact one (https://github.com/pact-foundation/pact-workshop-js).

👩‍🔧 Technical Design Notes

Suggest using the JS provider as the "backend" for the workshop, to both reduce the effort required in this workshop and

In order to test soap like api's (using XML for their body) a gandalf.pathing.Extractor that supports XPath is required.