basepath in swagger is ignored
Description:
Steps to reproduce the issue:
- Create a basepath in swagger file for an API
- Deploy the API using SAM
Observed result: "basepath" is always ignored. This forces us to rework our existing swaggers to use the "path" field.
Expected result: Allow different import options for basePath which is described from the AWS doc: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-import-api-basePath.html
Hello, it seems it's not related to SAM because I'm experiencing the same issue when I create an API in API Gateway with a Swagger file.
By default, basePath is ignored in swagger when an API is created. I am suggesting to add the support in SAM to allow prepend.
@mburket Do you have an example of how you would like to use the prepend property, and how it could look in SAM? I'm marking this as a feature request; with more information we could put it into our backlog or someone in the community could submit a PR implementing this feature.
@keetonian Thank you for looking into this issue. How about a new property named "DefinitionBathPath" for the resource of "AWS::Serverless::Api"? The acceptable values can be: "ignore", "prepand", "split".
Any updates on this issue?
I can file a PR to support this feature. Could you assign this issue to me? @keetonian @praneetap