Below are the five key terms that you need to know. These are Declare, Init, Plan, apply, and destroy.
The first step is declaring the resources. You can do this in any directory where no other details should be present. It is not a command. It is just an initial step to declaring resources.
- terraform isn’t aware of your workspace, let alone that it’s supposed to create or manage anything, because it hasn’t been initialized.
- Terraform configuration must always be initialized at least once, but you may have to initialize again if you add new providers or modules.
- Don’t fret about when to run
init, because Terraform will always remind you. Moreover,
initis an idempotent command, which means you can call it as many times as you want in a row with no side effects.
$ terraform init
After initialization, Terraform creates a hidden .terraform directory for installing plugins and modules.
- Terraform intends to do this by running
plan. You should always run
terraform planinforms you about what Terraform intends to do and acts as a linter, letting you know about any syntax or dependency errors.
- It’s a read-only action that does not alter the state of deployed infrastructure, and like
init, it’s idempotent.
The apply command compares the output against the generated execution plan.
In the terraform destroy, first generates an execution plan as if there were no resources in the configuration files by performing a Read() on each resource and marking all existing resources for deletion.
$ terraform destroy -auto-approve
The optional flag
destroy, which is exactly the same as for; it automatically approves the result of the execution plan.