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

Lambda trigger not attached with API Gateway route #43

Closed AlexBatorykLeliw closed 2 years ago

AlexBatorykLeliw commented 2 years ago

Description

Please provide a clear and concise description of the issue you are encountering, your current setup, and what steps led up to the issue. If you can provide a reproduction, that will help tremendously.

⚠️ Note

Before you submit an issue, please perform the following first:

  1. Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
  2. Re-initialize the project root to pull down modules: terraform init
  3. Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Reproduction

Steps to reproduce the behavior:

No Yes terraform apply ### Code Snippet to Reproduce

image

Expected behavior

The attachment in API Gateway is correct, expect to see the lambda trigger appear in the AWS Console (see image) image

Actual behavior

The trigger is not present and the resultant API calls result in: 500 Internal Error. When I detach and re-attach in the AWS Console, the trigger does show after a refresh and API calls work

Terminal Output Screenshot(s)

Additional context

github-actions[bot] commented 1 year ago

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.