title: Handling Terraform recreating AWS subnets that have load balancers attached causing a deadlock
body: <p>So I have two projects, separated and isolated from each other, using separate terraform state files to manage themselves.</p>
  
  <p><strong>Project A:</strong> The VPC, networking, subnets, eip, gw layer. This project is a shared VPC for all projects in my working group. We launch all our projects within this same VPC</p>
  
  <p><strong>Project B:</strong> The application, load balancers, security groups, ecs containers, api-gateway. This project is the application itself, you configure the load balancer accordingly with the security groups that allow whatever ports it needs and runs the software on ecs.</p>
  
  <p><strong>The problem:</strong>
  When I wanted to change a few small things in the VPC configuration, not even actual information, just some names of resources, it seems I accidentally triggered a recreate of the subnets. This means it'll try to delete them. But it can't because there are load balancers attached to it. So it constantly fails. It's deadlocked now cause I have 20 projects deployed each with their own load balancer</p>
  
  <p>How do I manage this so the VPC can be reconfigured without always triggering problems that cause me to have to destroy and recreate the whole application suite each time. This seems a really annoying problem to always have to think of that solution when in my case, I actually didn't change anything in the subnets, just normalised the terraform resource names.</p>