Terraform Cheat Sheet
Omar Ismail
Senior Software Engineer @ Digitinary | Java 8 Certified? | Spring & Spring Boot?????? | AWS? | Microservices ?? | RESTFul Apis & Integrations ?? FinTech ?? | Open Banking ?? | Digital Payments and Transformation??
Thanks to the original writer and article :
https://itnext.io/terraform-cheat-sheet-3f7c5c55cfbc
Sometimes you just want to get straight to the commands you need to use with a particular tool, without having to trawl through all the documentation. In this post, I’ll highlight the commonly used commands used on the Terraform CLI so you can get straight into the action without the pain!
This command reference guide was written using the latest version of Terraform at the time of writing, v.1.1.9. New commands and subcommands can be added and depreciated over time with different versions, but should not change too dramatically. You can get the latest version of Terraform here:
Terraform command quick reference
Contents
Get Help
terraform -help?— Get a list of available commands for execution with descriptions. Can be used with any other subcommand to get more information.
terraform fmt -help?— Display help options for the?fmt?command.
Show your Terraform version
terraform version?— Shows the current version of your Terraform and notifies you if there is a newer version available for download.
Format your Terraform code
This should be the first command you run after creating your configuration files to ensure your code is formatted using the HCL standards. This makes it easier to follow and aids collaboration.
terraform fmt?— Format your Terraform configuration files using the HCL language standard.
terraform fmt --recursive?— Also formats files in subdirectories
terraform fmt --diff?— Display differences between original configuration files and formatting changes.
terraform fmt --check?— Useful in automation CI/CD pipelines, the check flag can be used to ensure the configuration files are formatted correctly, if not the exit status will be non-zero. If files are formatted correctly, the exit status will be zero.
Initialize your directory
terraform init?— In order to prepare the working directory for use with Terraform, the?terraform init?command performs Backend Initialization, Child Module Installation, and Plugin Installation.
terraform init -get-plugins=false?— Initialize the working directory, do not download plugins.
terraform init -lock=false?— Initialize the working directory, don’t hold a state lock during backend migration.
terraform init -input=false?— Initialize the working directory, and disable interactive prompts.
terraform init -migrate-state?— Reconfigure a backend, and attempt to migrate any existing state.
terraform init -verify-plugins=false?— Initialize the working directory, do not verify plugins for Hashicorp signature
For a detailed rundown of the?terraform init?command see?my post here!
Download and install modules
Note this is usually not required as this is part of the?terraform init?command.
terraform get?— Downloads and installs modules needed for the configuration.
terraform get -update?— Checks the versions of the already installed modules against the available modules and installs the newer versions if available.
Validate your Terraform code
terraform validate?— Validates the configuration files in your directory, and does not access any remote state or services.?terraform init?should be run before this command.
Plan your Infrastructure
terraform plan?— Plan will generate an execution plan, showing you what actions will be taken without actually performing the planned actions.
terraform plan -out=<path>?— Save the plan file to a given path. Can then be passed to the?terraform apply?command.
terraform plan -destroy?— Creates a plan to destroy all objects, rather than the usual actions.
Deploy?your?Infrastructure
terraform apply?— Creates or updates infrastructure depending on the configuration files. By default, a plan will be generated first and will need to be approved before it is applied.
terraform apply -auto-approve?— Apply changes without having to interactively type ‘yes’ to the plan. Useful in automation CI/CD pipelines.
terraform apply <planfilename>?— Provide the file generated using the?terraform plan -out?command. If provided, Terraform will take the actions in the plan without any confirmation prompts.
terraform apply -lock=false?— Do not hold a state lock during the Terraform apply operation. Use with caution if other engineers might run concurrent commands against the same workspace.
terraform apply -parallelism=<n>?— Specify the number of operations run in parallel.
terraform apply -var="domainpassword=password123"?— Pass in a variable value.
terraform apply -var-file="varfile.tfvars"?— Pass in variables contained in a file.
terraform apply -target=”module.appgw.0"?— Apply changes only to the targeted resource.
Destroy?your?infrastructure
terraform destroy?— Destroys the infrastructure managed by Terraform.
terraform destroy -target=”module.appgw.0"?— Destroy only the targeted resource.
terraform destroy -auto-approve?— Destroys the infrastructure without having to interactively type ‘yes’ to the plan. Useful in automation CI/CD pipelines.
领英推荐
‘Taint’ or ‘Untaint’ your resources
Use the?taint?command to mark a resource as not fully functional. It will be deleted and re-created.
terraform taint vm1.name?— Taint a specified resource instance.
terraform untaint vm1.name?— Untaint the already tainted resource instance.
Refresh the state file
terraform refresh?— Modifies the state file with updated metadata containing information on the resources being managed in Terraform. Will not modify your infrastructure.
View?your?state file
terraform show?— Shows the state file in a human-readable format.
terraform show <path to statefile>?— If you want to read a specific state file, you can provide the path to it. If no path is provided, the current state file is shown.
Manipulate?your?state file
terraform state?— One of the following subcommands must be used with this command in order to manipulate the state file.
terraform state list?— Lists out all the resources that are tracked in the current state file.
terraform state mv?— Moves an item in the state, for example, this is useful when you need to tell Terraform that an item has been renamed, e.g.?terraform state mv vm1.oldname vm1.newname
terraform state pull > state.tfstate?— Gets the current state and outputs it to a local file.
terraform state push?— Update remote state from the local state file.
terraform state replace-provider hashicorp/azurerm customproviderregistry/azurerm?— Replace a provider, useful when switching to using a custom provider registry.
terraform state rm?— Remove the specified instance from the state file. Useful when a resource has been manually deleted outside of Terraform.
terraform state show <resourcename>?— Show the specified resource in the state file.
Import existing Infrastructure into your Terraform state
terraform import vm1.name -i id123?— Import a VM with id123 into the configuration defined in the configuration files under vm1.name.
terraform import vm1.name -i id123 -allow-missing-config?— Import and allow if the configuration block does not exist.
Get provider information
terraform providers?— Displays a tree of providers used in the configuration files and their requirements.
Manage your workspaces
terraform workspace?— One of the following subcommands must be used with the workspace command. Workspaces can be useful when an engineer wants to test a slightly different version of the code. It is not recommended to use Workspaces to isolate or separate the same infrastructure between different development stages, e.g. Dev / UAT / Production, or different internal teams.
terraform workspace show?— Show the name of the current workspace.
terraform workspace list?— List your workspaces.
terraform workspace select <workspace name>?— Select a specified workspace.
terraform workspace new <workspace name>?— Create a new workspace with a specified name.
terraform workspace delete <workspace name>?— Delete a specified workspace.
View your outputs
terraform output?— Lists all the outputs currently held in your state file. These are displayed by default at the end of a?terraform apply?, this command can be useful if you want to view them independently.
terraform output -state=<path to state file>?— Lists the outputs held in the specified state file.
terraform output -json?— Lists the outputs held in your state file in JSON format to make them machine-readable.
terraform output vm1_public_ip?— List a specific output held in your state file.
Release a lock on your workspace
terraform force-unlock <lock_id>?— Remove the lock with the specified lock ID from your workspace. Useful when a lock has become ‘stuck’, usually after an incomplete Terraform run.
Log in and out to a remote host (Terraform Cloud)
terraform login?— Grabs an API token for Terraform cloud (app.terraform.io) using your browser.
terraform login <hostname>?— Log in to a specified host.
terraform logout?— Removes the credentials that are stored locally after logging in, by default for Terraform Cloud (app.terraform.io).
terraform logout <hostname>?— Removes the credentials that are stored locally after logging in for the specified hostname.
Produce a dependency diagram
terraform graph?— Produces a graph in DOT language showing the dependencies between objects in the state file. This can then be rendered by a program called Graphwiz (amongst others).
terraform graph -plan=tfplan?— Produces a dependency graph using a specified plan file (generated using?terraform plan -out=tfplan?).
terraform graph -type=plan?— Specifies the type of graph to output, either?plan, plan-refresh-only, plan-destroy,?or?apply?.
Test your expressions
terraform console?— Allows testing and exploration of expressions on the interactive console using the command line. e.g. 1+2 :)
Summary
This guide should help you get straight to the command you need when using the Terraform CLI!