-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
More than one consumer causes VerifyProvider
to fail when specifying BrokerURL
#75
Comments
BrokerURL
VerifyProvider
to fail when specifying BrokerURL
Thanks @sugarjig, will take a look. |
Hi @sugarjig, I've pushed a fix for this. Could you please take a look at https://github.com/pact-foundation/pact-go/releases/tag/v0.0.12 and see if it addresses your issue? The pact integration test just verified a new consumer I added to the broker, so this confirms that we can verify multiple consumers now. |
Thanks! I will give it a try. Any idea when v0.0.12 will be finalized? I have noticed that the tag keeps moving... |
The fix worked! I think until v0.0.12 is finalized, and the tag is stable, we can't update. We have a workaround where we're specifying the consumers, and calling |
Great! I was just waiting confirmation, I'll push out a stable release today. |
I've released v0.0.12 now, the tag won't move. FYI going forward no tags should move as the build /release process is drastically changing. Also if you're keen, checkout v0.0.13-beta which is a new daemonless branch and will have support for async messaging. |
Awesome! Daemonless operation sounds great. I'll have to give it a try. Thanks again! |
Thanks - feedback welcome. We have a Slack channel pact-foundation.slack.com where you can chat with us (moving away from Gitter), let us know if you'd like an invite (we don't have an auto-invite thing setup just yet). |
Software versions
Expected behaviour
When calling
pact.VerifyProvider
and passing in atypes.VerifyRequest
withBrokerURL
specified, I expect that if the broker contains pacts from more than one consumer for this provider, each pact will be verified.Actual behaviour
When running the test, I see the following output:
Steps to reproduce
The text was updated successfully, but these errors were encountered: