-
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
aws_apigateway: Method responses from default method options set on RestApi not passed to Methods #26252
Comments
This line is probably the issue
Think it should be |
|
…t passed to Method (aws#26275) `methodResponses` specified in `RestApi`'s `defaultMethodOptions` were not passed to `Method` as default. This fix solves the problem. Closes aws#26252. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…t passed to Method (aws#26275) `methodResponses` specified in `RestApi`'s `defaultMethodOptions` were not passed to `Method` as default. This fix solves the problem. Closes aws#26252. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Describe the bug
When creating a
RestApi
and settingRestApiProps.defaultMethodOptions.methodResponses
, the method responses aren't passed to methods created on theRestApi
that don't have aMethodOptions
passed in.Expected Behavior
Method responses should be passed to methods.
Current Behavior
Method responses aren't passed to methods. Other properties like
RestApiProps.defaultMethodOptions.authorizationType
seem to be passed though.Reproduction Steps
TypeScript code:
Resulting
AWS::ApiGateway::Method
:CDK CLI Version
2.85.0
Framework Version
2.85.0
Node.js Version
20.2.0
OS
macOS Monterey 12.6.6 and Amazon Linux 2
Language
Typescript
Language Version
5.1.3
Other information
If we pass in the integration and method options when creating the method, the resulting template is as expected.
TypeScript code:
Resulting
AWS::ApiGateway::Method
:The text was updated successfully, but these errors were encountered: