Multiple providers with shared consumers about pact-specification

[uglyog]

Atlassian have built a tool that can verify pact files against a swagger (or Open API) spec. See https://bitbucket.org/atlassian/swagger-request-validator

[bethesque]

At a scale of 200 consumers, I don't think pact is the best option. Its purpose is to allow the consumers' requirements to drive the provider implementation, and to allow rapid changes with confidence to the provider, avoiding the traditional versioning approach. It's sweet spot is internal APIs. With 200 consumers, you're basically a public API, and you're going to have to provide stable versions, and move at a slower pace because there's no way 200 codebases will be able to keep up with rapid change. Driving out the requirements will be more of a long winded people process rather than a "lets have a quick chat and whip up a potential contract" kind of process.