fix: Integration URI is not always a lambda_arn

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: Integration URI is not always a lambda_arn #15

Closed stefan-rgb closed 3 years ago

stefan-rgb commented 3 years ago

Description

the integration uri must not always be lambda

Motivation and Context

currently you would use "lambda_arn" attribute also for http-proxy integrations

Breaking Changes

How Has This Been Tested?

changed it locally within the cached module and executed my terraform successfully

antonbabenko commented 3 years ago

Thanks!

v0.6.0 has been just released.

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.