-
Notifications
You must be signed in to change notification settings - Fork 4k
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
apigateway: missing support for models #1695
Labels
@aws-cdk/aws-apigateway
Related to Amazon API Gateway
feature-request
A feature should be added or improved.
Comments
eladb
added
feature-request
A feature should be added or improved.
@aws-cdk/aws-apigateway
Related to Amazon API Gateway
labels
Feb 11, 2019
Starting to look into this one. |
👍 |
I've been slow at working on this. Think I've got most of the changes sorted out. Just trying to wrap enough testing around creating and consuming models. Will try to get a PR open soon, to get some discussion going. |
Thanks for the update! Looking forward |
4 tasks
PR #2102 has been opened to address this issue. |
4 tasks
eladb
pushed a commit
that referenced
this issue
Jun 27, 2019
…d validators (#2960) Fixes #905: "apigateway: "methodResponses" is missing from MethodOptions" Fixes #1695: apigateway: missing support for models Fixes #727: API Gateway: improve API for request parameters and responses Fixes #723: API Gateway: missing features Fixes #2957: RestApi to use logical id as a name for APIs instead of name of current construct Adds support for JsonSchema in Model Aligns Model to the PhysicalName convention. No breaking change, documentation updated
This was referenced Aug 22, 2019
This was referenced Dec 12, 2019
This was referenced Sep 24, 2024
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-apigateway
Related to Amazon API Gateway
feature-request
A feature should be added or improved.
When defining a REST API with API gateway, we can't currently define a collection of models that can be used to map response payloads from an integration to what is returned to a client.
https://docs.aws.amazon.com/apigateway/latest/developerguide/models-mappings.html
#1572 introduces the base support for MethodResponses, but only gives the functionality to use the default provided
Empty
andError
models that are generated, when you create a REST API. This work should be continued to provide full support for defining models.The text was updated successfully, but these errors were encountered: