-
Notifications
You must be signed in to change notification settings - Fork 0
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
Terraform Forces New Resource each time #7
Comments
Security Groups could be due to the following... I have been using Security Groups instead of vac_security groups. Testing |
The instance ID appears to be related to Using elements seems to force a new build (and destroy the old) Testing ListVar as noted in link above. |
Fixed by changing: subnet_id = "${element(var.public-subnets, count.index)}" to ..... I can now create upto as many machines as I state subnets... an improvement on how I would create 4 machines if only 3 subnets listed would be useful. |
Closing... improvement can be put on backlog. |
Each time I run my plan, my existing servers are destroyed and new ones built. Looking through the log a number of entries have 'forces new resource' next to them... listed below
-/+ aws_instance.Web[0] (new resource required)
id: "i-0b5e13fdd020b0917" => (forces new resource)
security_groups.#: "0" => "1" (forces new resource)
security_groups.3026238325: "" => "sg-a7ec92df" (forces new resource)
The text was updated successfully, but these errors were encountered: