Use case

Currently, there is no way for users to specify the top-level externalDocs property in the OpenAPI schema generation, despite having an existing data model for ExternalDocumentation in the repository. This issue proposes adding an argument to the configure_openapi() and enable_swagger() methods that allows users to pass an ExternalDocumentation object, enabling them to include links to external documentation in the generated OpenAPI specification as defined in the OpenAPI 3.1 specification.

Solution/User Experience

Add this field

Alternative solutions

Acknowledgment

• This feature request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET