-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Run deleteLingeringLambdaENIs when subnets are destroyed #4884
Conversation
applies the deleteLingeringLambdaENIs as well as the associated timeouts from resource_aws_security_group to resource_aws_subnet.
Hi @mmarod! I've rebased this locally and re-run the tests, it all looks good to me. I have some unrelated failures which I suspect are because my account has raised limits, and some tests which are skipped because my account does not support EC2 Classic, but I don't think any are related:
This will be landed shortly as 1ca811e (once I write a CHANGELOG) entry - I'm not sure if the pull request will update itself or not since I rebased it - the commit still gives you credit though! Thanks for opening a pull request - sorry it took so long to review! |
This has been released in version 1.38.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
The ENIs associated with lambda functions sometimes fail to delete. This applies the deleteLingeringLambdaENIs as well as the associated timeouts from resource_aws_security_group to resource_aws_subnet.
Fixes #829
Changes proposed in this pull request:
Output from acceptance testing (pretty sure these are fine):