hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.85k stars 9.19k forks source link

Terraform gets stuck at destroying security group #25663

Closed RichardBenes closed 1 month ago

RichardBenes commented 2 years ago

Hello,

as I was recently playing with Terraform and AWS, I found out that a certain change in the resource configuration makes Terraform get stuck at security group destruction.

I described the problem, including steps to reproduce here in the README.

It seems to be repeatable, I tried it two times with Terraform 1.2.3 and once with Terraform 1.2.4 after I found it out, and in each case the issue happened.

I used Terraform 1.2.4 on 64b Windows and hashicorp/aws v4.21.0.

Nevertheless, thanks you for providing such great tool!

tiborhercz commented 2 years ago

Looks like the same issue as described here: https://github.com/hashicorp/terraform-provider-aws/issues/265

Renkas commented 2 years ago

There are more details in: #2445

Although it is mentioned there that:

We know this is a frustrating issue for you all. Unfortunately, the Terraform dependency model doesn't yet support bi-directional dependencies between resources that would allow general modifying other resources as part of deletion or modification. We have an https://github.com/hashicorp/terraform/issues/16065 to address this.

This issue in the core seems to be addressed now so can we get this fixed already in aws security group deletion? @gdavison ?

github-actions[bot] commented 2 months ago

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

github-actions[bot] commented 2 weeks 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.