You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aws_eip resources should be destroyed when running terraform destroy
Actual Behavior
Terraform will recognize the resources on the next plan but will not destroy the resources either by removing the resource from the configuration or running terraform destroy
Output
$ tf apply
aws_eip.nat.1: Creating...
allocation_id: "" =>"<computed>"
association_id: "" =>"<computed>"
domain: "" =>"<computed>"
instance: "" =>"<computed>"
network_interface: "" =>"<computed>"
private_ip: "" =>"<computed>"
public_ip: "" =>"<computed>"
vpc: "" =>"true"
aws_eip.nat.0: Creating...
allocation_id: "" =>"<computed>"
association_id: "" =>"<computed>"
domain: "" =>"<computed>"
instance: "" =>"<computed>"
network_interface: "" =>"<computed>"
private_ip: "" =>"<computed>"
public_ip: "" =>"<computed>"
vpc: "" =>"true"
aws_eip.nat.0: Creation complete
aws_eip.nat.1: Creation complete
Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
$ tf destroy
Do you really want to destroy?
Terraform will delete all your managed infrastructure.
There is no undo. Only 'yes' will be accepted to confirm.
Enter a value: yes
Destroy complete! Resources: 0 destroyed.
Comments
I suspect perhaps the compact interpolation is affecting other resources. I came across this in an example and just removed using compact and make sure my lists have no spaces in between.
The text was updated successfully, but these errors were encountered:
nocode99
changed the title
aws_eip resources not destroyed when compact interpolation
aws_eip resources not destroyed when using compact interpolation
Sep 28, 2016
I just verified on master and with the new destroy branch being merged in that this no longer happens. Perhaps it was fixed recently but I tried your exact config (byte for byte) with a real AWS account and wasn't able to reproduce it in any scenario below:
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.
ghost
locked and limited conversation to collaborators
Apr 21, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
0.7.4
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Expected Behavior
aws_eip
resources should be destroyed when runningterraform destroy
Actual Behavior
Terraform will recognize the resources on the next
plan
but will not destroy the resources either by removing the resource from the configuration or runningterraform destroy
Output
Comments
I suspect perhaps the
compact
interpolation is affecting other resources. I came across this in an example and just removed using compact and make sure my lists have no spaces in between.The text was updated successfully, but these errors were encountered: