Amazon web services API网关与Lambda代理集成的API文档
我定义了一个SAM应用程序,在API网关后面有几个lambda“ 显然,API网关不太了解代理资源,例如:Amazon web services API网关与Lambda代理集成的API文档,amazon-web-services,swagger,aws-api-gateway,openapi,sam,Amazon Web Services,Swagger,Aws Api Gateway,Openapi,Sam,我定义了一个SAM应用程序,在API网关后面有几个lambda“ 显然,API网关不太了解代理资源,例如: 代理路径 请求模型 响应模型 API网关阶段生成的文档反映了这一点: swagger: "2.0" info: version: "1.0" title: "xxx-dev" host: "xxx.execute-api.us-west-2.amazonaws.com" basePath: &quo
- 代理路径
- 请求模型
- 响应模型
swagger: "2.0"
info:
version: "1.0"
title: "xxx-dev"
host: "xxx.execute-api.us-west-2.amazonaws.com"
basePath: "/dev"
schemes:
- "https"
paths:
/MyResource/{proxy+}:
post:
responses: {}
security:
- LambdaTokenAuthorizer: []
securityDefinitions:
LambdaTokenAuthorizer:
type: "apiKey"
name: "Authorization"
in: "header"
x-amazon-apigateway-authtype: "custom"
有没有办法向API网关提供缺少的位(代理路径、响应模型、请求模型)?
最终,我需要一个足够好的文档来生成客户机代码/允许一些集成测试。
这里有类似的问题->
swagger: "2.0"
info:
version: "1.0"
title: "xxx-dev"
host: "xxx.execute-api.us-west-2.amazonaws.com"
basePath: "/dev"
schemes:
- "https"
paths:
/MyResource/{proxy+}:
post:
responses: {}
security:
- LambdaTokenAuthorizer: []
securityDefinitions:
LambdaTokenAuthorizer:
type: "apiKey"
name: "Authorization"
in: "header"
x-amazon-apigateway-authtype: "custom"