Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

OAS validation fails if we have more than 1 proxy endpoint

I'm working on an Apigee proxy which has 2 different endpoints which have different base paths but provide similar functionality. Since the base path of the 2nd proxy endpoint is just '/' but the spec contains the full path, the OAS validation policy throws an error that 'POST operation is not available on the path.'. I have tried updating the request URL, the proxy path suffix but none of that works.
Infact as per the Apigee documentation if the <Source> is "message" it should consider the updated data for validation as per policies applied to it but this too doesn't work. It still considers the original proxy pathsuffix and throws the same error.
Is there a solution to either skip checking path for the proxy? Or considering the full URL/base path for OAS validation.

1 1 127
1 REPLY 1