question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add support for retrieving all pacts for a given provider

See original GitHub issue

Hi Neil! Rather than specifying one or more pact URLs, the provider name, and a list of consumer version tags can be specified, and the pact-provider-verifier will determine the right pacts to verify. This feature will be required for an upcoming feature release which will allow “pending pacts” to be verified without breaking the build. The --provider-version-tag will also be required for that feature. Here are the relevant bits of the CLI documentation.

Give me a yell if you need some clarification.

Usage:
  pact-provider-verifier PACT_URL ... -h, --provider-base-url=PROVIDER_BASE_URL

Options:
      [--provider=PROVIDER]
      [--consumer-version-tag=TAG]                                           # Retrieve the latest pacts with   this consumer version tag. Used in conjunction with --provider. May be specified multiple times.
      [--provider-version-tag=TAG]                                           # Tag to apply to the provider   application version. May be specified multiple times.

See:

https://github.com/pact-foundation/pact-provider-verifier#usage

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
bethesquecommented, Nov 22, 2019

Time to make an omelette!

0reactions
bethesquecommented, Jan 14, 2020

Thanks Neil 🙏

Read more comments on GitHub >

github_iconTop Results From Across the Web

Provider Verification | Pact Docs
To dynamically retrieve pacts from a Pact Broker for a provider, provide the broker URL, the name of the provider, and the consumer...
Read more >
Verifying Pacts | Pact Docs
Using the pact:verify task is the most common way to verify pacts. This is where you configure the default set of pacts that...
Read more >
Injecting values from provider states - Pactflow
The mechanism we use to setup validation test data is called Provider States. Essentially, these define the state the provider needs to be...
Read more >
Consumer Driven Contracts with Pact
Learn how to get started with Pact, a library for utilising Consumer Driven Contracts.
Read more >
Example Spring Boot project for the Pact workshop
Product Service (Provider). Provides useful things about products, such as listing all products and getting the details of an individual product.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found