We have a CI-CD pipeline that reads a swagger specs and converts it into reverse proxies in apigee Edge. We have a logic set in the pipeline that reads the value of the basepath tag in Swagger specs and sets it as the basepath of the reverse proxy API in apigee.
This leads to conflicts when two different API publishing teams ( that drop swagger specs to be picked up by the pipeline ) set the same basepath value in their swagger specs , since two Apigee proxies cannot have the same base path. Any ideas on how this can be resolved from a governance or solution standpoint ?
LinkedIn
Twitter
