dcee
New Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
AWS API Gateway Integration questions
Hi there What's best practice regarding the base path and host when setting up an AWS integration? We want the api on AWS to run on our own domain (api.domain.io) with a v1 basepath. But, we also want to be able to use the virtual mocking functionality. Is there a conflict here? Currently, the API is running on AWS using the default domain and basepath set by the automock plugin. It looks something like this (where CompanyName is the SwaggerHub organisation); https://api.domain.io/CompanyName/TestApi/1.0.0/inventory When we set up the integration, we set the proxy to the basepath given by the automock plugin. This is because we had issues with directing the domain name when we'd set the proxy to https://api.domain.io/v1. Also because the automock functionality stopped working when we set the base path and domain to our custom settings. Any tips? Cheers, Dave1.8KViews0likes1CommentOdd UI behaviour
I'm getting this message; Semantic error at paths./domains/{crawl_id} Declared path parameter "crawl_id" needs to be defined as a path parameter at either the path or operation level Jump to line 89 But there's no reference to crawl_id on line 89 or anywhere in the API... Also, when I open other API projects, the same error is showing on them as well. Any thoughts? Cheers, DaveSolved3.5KViews0likes4Comments