We are using separate Open API Specs for each vers...
# generalq
Quinton Miller
08/14/2023, 7:42 PMWe are using separate Open API Specs for each version of the provider API, meaning the spec file is unique for each version of the API. When the provider deploys their code they support all of these versions as long as the consumer supplies the version in the header when making the API call. Does BDC require all versions of the API to be in a single Open API spec file or can each version of the provider have their own spec file?
Quinton Miller
08/14/2023, 9:09 PM@Matt (pactflow.io / pact-js / pact-go)
m
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 9:30 PM
Yes in that case it should be a single OAS
Matt (pactflow.io / pact-js / pact-go)
08/14/2023, 9:31 PM
The OAS should represent the deployed unit
t
Timothy Jones
08/14/2023, 10:58 PMThis question belongs in #CLS16AVEE