-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS integration with Swagger does not seem to consider basePath #4402
Comments
Hi @arichiardi 👋 Sorry you're running into trouble here. Does Swagger's |
Oh so are you just sending the json to them? I thought terraform was doing the parsing. |
Correct, we just upload the JSON to the API: Given this looks like broken functionality of the API Gateway API, I'm going to close this issue for now but do not hesitate to reply back if there's something amiss with the provider handling here. |
Perfect thank you |
I also encountered this issue and was able to find a work around by adding the basePath to each individual path. e,g However, according to the AWS CLI it is possible for the basePath to actually have an effect by using a parameter.
For details: https://forums.aws.amazon.com/thread.jspa?messageID=885830&tstart=0 @bflad would you mind reviewing? |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This has been released in version 3.24.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
Terraform Version
Terraform v0.11.7
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
In the AWS Api Gateway I see:
But I think I should see:
ARN: arn:aws:execute-api:region:accountId:apiId/*/POST/prod/my-endpoint
where the
prod
is read from the Swagger'sbasePath
, according to https://swagger.io/docs/specification/2-0/api-host-and-base-path.Actual Behavior
What actually happened?
Steps to Reproduce
Try a
swagger.json
withbasePath
set.Important Factoids
There are workarounds I think, still worth signaling.
The text was updated successfully, but these errors were encountered: