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
{{ message }}
This repository has been archived by the owner on Oct 8, 2020. It is now read-only.
Currently, when there is an issue with a template file like having a variable being used in the file that was not specified as input, terraform only fails at the apply phase. Then you have to destroy the infrastructure that is already created so far, fix the issue in the template file and then apply again. This can be time-consuming if you are creating many resources.
Attempted Solutions
Currently, you have to terraform destroy, fix the file and then terraform applyagain
Proposal
I think it would be great if Terraform validates the template files before starting applying all the changes, this way we can make sure it will not break during infrastructure creation.
The text was updated successfully, but these errors were encountered:
This issue was originally opened by @fcappi as hashicorp/terraform#20770. It was migrated here as a result of the provider split. The original body of the issue is below.
Current Terraform Version
Use-cases
Currently, when there is an issue with a template file like having a variable being used in the file that was not specified as input, terraform only fails at the apply phase. Then you have to destroy the infrastructure that is already created so far, fix the issue in the template file and then apply again. This can be time-consuming if you are creating many resources.
Attempted Solutions
Currently, you have to
terraform destroy
, fix the file and thenterraform apply
againProposal
I think it would be great if Terraform validates the template files before starting applying all the changes, this way we can make sure it will not break during infrastructure creation.
The text was updated successfully, but these errors were encountered: