serverless-openapi-documentation
serverless-openapi-documentation copied to clipboard
temando
Serverless 1.0 plugin to generate OpenAPI V3 documentation from serverless configuration
- no longer using `@jdw/jst` to dereference schema - instead referenced schemas are included in `openapi`'s `components` and referenced accordingly - major version bump as produced document is now different...
Hi, I am using HTTP API instead of the usual REST API for AWS Gateway. While doing so, no documentation gets generated. So is there no support for HTTP API?...
I've forked and hopefully improved upon this project here: https://github.com/JaredCE/serverless-openapi-documenter Would love it if people started using this and giving me feedback. There might be some gotchas with a straightforward...
In Swagger 2 plugin I can reference models in other models. Most commonly, when an endpoint response model is an array containing item models. See the [issue at the serverless-aws-documentation](https://github.com/9cookies/serverless-aws-documentation/pull/58)....
Issue described here: https://stackoverflow.com/questions/64117950/how-to-use-serverless-openapi-documentation-with-serverless-typescript-template
`serverless.yml` ``` org: yeukfei05 app: random-user-api-serverless service: random-user-api-serverless frameworkVersion: '2' useDotenv: true provider: name: aws runtime: nodejs14.x stage: prod region: ap-southeast-1 apiName: random-user-api-serverless-prod tracing: apiGateway: true lambda: true environment: NODE_ENV:...
Just installed this plugin for my serverless project and get this error after generating for the first time:  Thinking a conflict with another plugin? I've noticed the project is...
The project is clearly abandoned by upstream as stated by the maintainer in https://github.com/temando/serverless-openapi-documentation/pull/27#issuecomment-417289664 > This repo has naturally regressed into a state of deprecation as we at Temando have...
This pull request fixes the following deprecation warning: ``` CLI options definitions were upgraded with "type" property (which could be one of "string", "boolean", "multiple"). Below listed plugins do not...
Is there any possibility to specify `servers` section for the generated documentation? Some docs: - https://swagger.io/docs/specification/basic-structure/ - https://swagger.io/docs/specification/api-host-and-base-path/
