search

terraform-aws-modules / terraform-aws-apigateway-v2

Terraform module to create AWS API Gateway v2 (HTTP/WebSocket) 🇺🇦
https://registry.terraform.io/modules/terraform-aws-modules/apigateway-v2/aws
Apache License 2.0
144 stars 188 forks source link

fix: default API Gateway integration method #14

Closed abemedia closed 3 years ago

abemedia commented 3 years ago

Description

Integration method ANY is not supported. The reason you can't see it on the AWS Console is because it always defaults to POST. The has nothing to do with the HTTP method used to call the API and is just how API Gateway calls the Lambda API (the handler will still receive the correct method).

Motivation and Context

Lambda proxy integrations were broken upon first deployment of our services, but worked as soon as they were edited and saved in the console (without making any changes). I investigated and realised that it's because an unsupported integration method was used and upon editing and saving the console automatically changed this to POST.

Breaking Changes

No

How Has This Been Tested?

Currently used in production in the company where I work.

antonbabenko commented 3 years ago

Thanks for the clarification and for the fix!

v0.7.0 has been just released.

abemedia commented 3 years ago

My pleasure!

github-actions[bot] commented 1 year ago

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.