Hi Pactflow team, I'm currently exploring bi-directional contract testing but I'm a bit confused in terms of supported provider contract formats. https://docs.pactflow.io/docs/bi-directional-contract-testing/provider - here, only OAS formats are mentioned. https://docs.pactflow.io/docs/bi-directional-contract-testing - in the video here, OAS is mentioned as one of the possibilities. However, it's not mentioned what other formats are supported. https://docs.pactflow.io/docs/bi-directional-contract-testing/publishing#publishing - in the CLI reference, I can see the parameter

--specification=SPECIFICATION

but there are no mentions about possible values (apart from OAS) so, the question is: is OAS the only format that's supported?

Yes, OAS is currently the only type at the moment

thanks for the clarification, @Matt (pactflow.io / pact-js / pact-go) ! our case is the following: we have a bunch of services that communicate with each other via a bunch of different APIs. For example, apart from REST, we have JSON-RPC (which isn't compatible with OAS) and GRPC. the idea was to leverage bi-directional contract testing to get a full overview of the contracts between services and compatibility of different versions (and also use

can-i-deploy

) in one place (pact flow) using our mocking framework (on the consumer side) we can generate the interactions according to the pact specification. I was hoping that there is also some kind of generic schema for provider. based on that, we'd be able to generate provider contracts.

Thanks for sharing. For now, you'd need to stick with Pact for that kind of testing

you'd need to stick with Pact for that kind of testing

do you mean consumer-driven contract testing?

Yes