-
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
[Bug]: Error deleting EC2 Network ACL rule on a destroying plan #34462
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @cristhianramirezp 👋 Thank you for taking the time to raise this! Are you able to supply debug logs (redacted as needed) so that whoever picks this up has the information necessary to look into this? |
This functionality has been released in v5.41.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 issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.5.2
AWS Provider Version
5.15.0
Affected Resource(s)
aws_network_acl
Expected Behavior
It is expected in normal behavior that resources are destroyed naturally without problems.
Actual Behavior
After several tests with Atlantis and running Terraform locally in the container, we came to the conclusion that there is an ongoing issue with the assume_role functionality which is causing conflicts with the API calls during a destroy.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
terraform init
terraform plan
terraform apply : Create resources with terraform apply
terraform - --destroy : Try to destroy acl_rule
Debug Output
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: