-
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
Optionally replace Lambda function ENI security groups on destroy #29289
Optionally replace Lambda function ENI security groups on destroy #29289
Conversation
Community NoteVoting for Prioritization
For Submitters
|
767ba70
to
b336899
Compare
adds the optional replace_security_groups_on_destroy and replacment_security_group_ids attributes
b336899
to
4fadf46
Compare
This functionality has been released in v4.54.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Description
Adds optional
replace_security_groups_on_destroy
andreplacement_security_group_ids
attributes to speed up lambda security group destruction under certain conditions. This implementation largely follows the design of thelocal-exec
provisioner described in this comment.Some caveats to this feature:
aws_subnet
destroy times. Subnets containing ENIs from deleted lambda functions will still depend on AWS's internal cleanup process. Be sure to preserve the appropriate IAM permissions on the lambda execution role to allow the Lambda service to clean these up.Relations
Relates #10329
Output from Acceptance Testing