More than one consumer causes `VerifyProvider` to fail when specifying `BrokerURL` about pact-go HOT 8 CLOSED

Awesome! Daemonless operation sounds great. I'll have to give it a try. Thanks again!

from pact-go.

Thanks @sugarjig, will take a look.

from pact-go.

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.

from pact-go.

Thanks! I will give it a try. Any idea when v0.0.12 will be finalized? I have noticed that the tag keeps moving...

from pact-go.

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 VerifyProvider for each one.

from pact-go.

Great! I was just waiting confirmation, I'll push out a stable release today.

from pact-go.

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.

from pact-go.

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).

from pact-go.