Giulio Giovannini
05/25/2023, 8:51 AM/mybaseurl/resource
while the provider Open API Spec yaml starts with a servers parameter like:
servers:
- url: /mybaseurl
and then defines the resource as:
/resource
post:
...
Pactflow can not match the paths as it disregards the servers parameter. The open Api Spec is autogenerated by Springboot so I can not change it that much.
Is there a workaround for this?Yousaf Nabi (pactflow.io)
05/25/2023, 9:20 AMThe open Api Spec is autogenerated by Springboot so I can not change it that much.You can, that is the major selling point of using a machine readable specification
Is there a workaround for this?I would assume as an initial pass, it would be to add the path on servers.url[0] into the front of each of your path entries
Giulio Giovannini
05/25/2023, 10:03 AMYousaf Nabi (pactflow.io)
05/25/2023, 10:11 AMGiulio Giovannini
05/25/2023, 11:13 AMYousaf Nabi (pactflow.io)
05/25/2023, 11:39 AMBut editing a OAS that was auto-generated to make it match the consumer contract looks a bit of a hack.You’d be surprised at the amount of auto-generated OAS’s that do need work to be usable/human readable
Giulio Giovannini
05/25/2023, 12:26 PMMatt (pactflow.io / pact-js / pact-go)
05/25/2023, 10:25 PM