-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for retrieving all pacts for a given provider #223
Comments
@bethesque Will try get this in the next couple of days |
@bethesque So what should be supplied as the |
Nothing - it's optional. Either you specify a PACT_URL, or you specify the broker URL and the provider name. Though, if you want, you can specify all of them, and it will fetch the pact by URL and dynamically fetch the pacts by name from the broker as well. If you really wanted. |
We don't actually use the PACT_BROKER_BASE_URL at all. All broker stuff is currently just setup with PACT_URL (which is currently mandatory in the DSL), so I'm going to need to change things a bit by the sounds of it. |
Time to make an omelette! |
Sorry to hassle you on this Neil, but we've got the new "pacts for verification" API and "pending pacts" stuff coming out soon that's going to rely on these fields. If you can find the time, I'd really appreciate it. |
@bethesque Sorry, completely forgot about this one! Will see what I can do. |
Released in |
Thanks Neil 🙏 |
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.
See:
https://github.com/pact-foundation/pact-provider-verifier#usage
The text was updated successfully, but these errors were encountered: