The article misses a key bit of information TF needs when making a plan:
4. The previous Terraform configuration
This is effectively stored by state.
We need this because if a resource is removed from the new config then Terraform needs to be able to delete the existing resource from the world. If we don’t have the state then Terraform must either:
1. Not delete it from the world
2. Or risk deleting something not managed by Terraform
If everything were managed by Terraform then perhaps we would not need state, but this is not realistic in my view.
We need this because if a resource is removed from the new config then Terraform needs to be able to delete the existing resource from the world. If we don’t have the state then Terraform must either:
If everything were managed by Terraform then perhaps we would not need state, but this is not realistic in my view.