<@U9UUY3CU9>: Are there any alternatives you would...
# pactflows
Sashi Kandru
08/15/2023, 12:12 PM@Matt (pactflow.io / pact-js / pact-go): Are there any alternatives you would suggest on how to approach this? Currently we have a separate OAS for each version of the code, Is BDC approach possible with separate OAS? https://pact-foundation.slack.com/archives/C5F4KFKR8/p1692042155313029
Sashi Kandru
08/15/2023, 12:13 PMCC: @Quinton Miller
m
Matt (pactflow.io / pact-js / pact-go)
08/15/2023, 12:41 PM
No, the OAS for a given version of a provider (version being an independently deployable thing) must fully describe it. If there are multiple APIs it supports spread across multiple OAS files, they must be merged. If they are separately deployed, they might be best modelled as different providers (i.e. unique name in Pactflow)
Matt (pactflow.io / pact-js / pact-go)
08/15/2023, 12:43 PM
The workarounds are to merge them (there are plenty of tools that can do this, it's probably quite straightforward without a dedicated tool) or separate the apps out logically in Pactflow
👍 1