Initialising a working directory 12
| Command | What it does |
|---|---|
terraform init | Initialise the working directoryFirst command to run in a new or cloned configuration; sets up the backend, modules and providers and is safe to repeat. |
terraform init -upgrade | Upgrade modules and providersInstalls the newest versions the constraints allow, ignoring the selections saved in the dependency lock file. |
terraform init -backend-config=PATH | Pass backend settingsMerges an HCL file or a single key=value pair into the backend block; repeat the option for more values. |
terraform init -reconfigure | Reconfigure the backendDiscards the stored backend settings and does not migrate existing state. |
terraform init -migrate-state | Migrate state to a new backendSwitches to the changed backend settings and tries to copy the current state across, asking for confirmation where needed. |
terraform init -force-copy | Skip state copy promptsAnswers yes to every question about copying state when a new backend is initialised. |
terraform init -backend=false | Skip backend initialisationPrepares a directory for validate without contacting a remote backend; anything initialised earlier stays in use. |
terraform init -input=false | Disable init promptsA step that needs an answer then fails with an error instead of waiting. |
terraform init -get=false | Skip module downloadLeaves child modules alone; meant for directories whose module tree is already installed. |
terraform init -from-module=SOURCE | Copy a module before initCopies the named module into an empty target directory, then initialises it. |
terraform init -lockfile=MODE | Set the lock file modeThe only mode is readonly, which verifies checksums against the lock file without changing it. |
terraform init -json | Print init progress as JSONReplaces the human-readable log with JSON messages for other programs to read. |
Planning and applying 16
When no saved plan file is passed, apply accepts every planning mode and planning option of plan, including -destroy, -refresh-only, -replace, -var and -var-file.
| Command | What it does |
|---|---|
terraform plan | Preview the changesCompares the configuration with real infrastructure and prints the proposed actions without carrying any of them out. |
terraform plan -out=PATH | Save the plan to a fileThe saved file can be handed to apply later, so exactly the reviewed actions are carried out. |
terraform apply | Apply the changesCreates a new plan, shows it and waits for approval before creating, updating or deleting anything. |
terraform apply PLAN | Apply a saved planCarries out the actions stored in a file written by plan -out, without asking for confirmation. |
terraform apply -auto-approve | Apply without the approval promptCovers destructive changes too; the flag is ignored when a saved plan file is passed. |
terraform destroy | Destroy all managed objectsA convenience alias for apply -destroy that removes everything the configuration manages. |
terraform apply -destroy | Apply in destroy modeThe full form that terraform destroy stands for; it takes the same options as apply. |
terraform plan -destroy | Preview a destroyShows what a destroy would remove, without executing it. |
terraform plan -refresh-only | Check for drift onlyReports where remote objects differ from the last apply, without proposing actions to undo that drift. |
terraform apply -refresh-only | Sync state with real objectsShows the differences found outside Terraform and asks before writing them to the state. |
terraform refresh | Refresh state (deprecated)Deprecated alias for apply -refresh-only -auto-approve, which rewrites the state with no chance to review. |
terraform plan -refresh=false | Skip the refresh stepPlans faster by not checking remote objects, at the risk of working from a stale state. |
terraform plan -lock=false | Plan without a state lockDangerous if another person or pipeline works on that workspace at the same moment. |
terraform apply -lock-timeout=0s | Set the lock wait timeKeeps retrying for the state lock for the given duration; 0s, the default, fails at once. |
terraform plan -parallelism=N | Limit concurrent operationsCaps how many operations run at once; the default is 10. |
terraform plan -compact-warnings | Shorten warning outputPrints only the summary line of each warning, as long as no errors accompany them. |
Variables and targeting 7
Terraform reports an error when a -var value has a space before or after its equals sign.
| Command | What it does |
|---|---|
terraform plan -var 'NAME=VALUE' | Set one input variableSingle quotes keep a Unix shell from altering the value; repeat the option for each further variable. |
terraform plan -var-file=FILENAME | Load variables from a fileReads a variables file on top of terraform.tfvars and *.auto.tfvars, which load automatically. |
export TF_VAR_region=us-west-1 | Set a variable from the environmentAny TF_VAR_ prefix followed by a variable name works; Terraform checks this source last. |
terraform plan -target=ADDRESS | Plan only one resourceRestricts the plan to the matching resource instances and what they depend on; meant for exceptional situations. |
terraform plan -replace=ADDRESS | Force replacement of an instancePlans a replace action for that instance where an update or no change would otherwise be planned. |
terraform apply -replace="aws_instance.example[0]" | Replace one instance on applyThe recommended successor to taint: the replacement appears in the plan before anything is changed. |
terraform destroy -target aws_instance.example | Destroy a single resourceDestroys just the aws_instance labelled example and its dependencies instead of the whole configuration. |
Formatting and validating 11
| Command | What it does |
|---|---|
terraform fmt | Format configuration filesRewrites the files in the current directory to the canonical style and lists the ones it changed. |
terraform fmt -check | Check formatting onlyWrites nothing and exits non-zero when any file needs formatting, naming those files. |
terraform fmt -diff | Show formatting diffsPrints each pending change as a diff, which helps when reviewing what fmt would alter. |
terraform fmt -recursive | Format subdirectories tooWithout it only the given directory, or the current one, is handled. |
terraform fmt -write=false | Leave source files untouchedReports formatting problems without rewriting anything; -check and standard input imply it. |
terraform fmt -list=false | Hide the changed-file listStops fmt from printing the names of files that are not in the standard style. |
terraform fmt - | Format standard inputA single dash as the target makes fmt read the configuration from stdin instead of scanning a directory. |
terraform validate | Validate the configurationChecks syntax and internal consistency in an initialised directory; remote state and provider APIs are not contacted. |
terraform validate -json | Validation result as JSONMeant for editor integrations and other tools; colour is always switched off. |
terraform validate -no-tests | Skip test filesChecks the configuration only and leaves the test files of the module unvalidated. |
terraform validate -query | Also validate query filesExtends the check to .tfquery.hcl files as well. |
Inspecting state and outputs 17
| Command | What it does |
|---|---|
terraform show | Show the current statePrints the latest state snapshot in readable form when no file path is given. |
terraform show FILE | Inspect a saved plan fileTakes the path of a plan or state file, so a saved plan can be read before it is applied. |
terraform show -json | State or plan as JSONSensitive values held in the state are printed in plain text in this format. |
terraform output | List root module outputsReads the values from the state file; outputs of child modules are not shown. |
terraform output NAME | Print one output valueAn output requested by name is printed unredacted even when it is marked sensitive. |
terraform output -json | Outputs as JSONThe stable format for scripts; a parser such as jq can pick values out of it. |
terraform output -raw NAME | Print an output as raw textWorks for string, number and boolean values only and adds no formatting, which suits shell scripts. |
terraform state list | List resources in stateLists every tracked resource address, root module first and deeper modules last. |
terraform state list ADDRESS | Filter the resource listShows only resources that match the given resource or module addresses. |
terraform state list -id=ID | Find a resource by IDKeeps only the instances whose id attribute equals the value given. |
terraform state show ADDRESS | Show one resource's attributesThe address has to point at a single resource in the state. |
terraform state show -json ADDRESS | Resource attributes as JSON |
terraform state identities -json | List resource identitiesPrints the identity of each resource instance as JSON; add addresses to filter by resource or module. |
terraform state pull | Print the raw stateFetches the state from wherever it is stored, upgrades it to the current file version and writes it to stdout. |
terraform graph | Print the dependency graphOutputs a simplified graph of the ordering between resources, written in the DOT language. |
terraform graph -type=plan | dot -Tpng >graph.png | Render the plan graph as PNGPipes the detailed plan graph into the Graphviz dot command, which must be installed. |
terraform graph -format=FORMAT | Choose the graph formatAccepts dot, which is the default, or mermaid. |
State surgery 12
Quotes inside a resource address, as in aws_instance.baz["key"], must be escaped on the command line so that the shell does not interpret them.
| Command | What it does |
|---|---|
terraform state | State subcommand groupParent of list, show, mv, rm, pull, push and replace-provider; subcommands that modify state write a backup file first. |
terraform state mv SOURCE DESTINATION | Rename or move a resourceTracks an existing object under a new address, for example after renaming a resource block or moving it into a module. |
terraform state mv -dry-run SOURCE DESTINATION | Preview a state moveReports the planned move and leaves the state as it is. |
terraform state rm ADDRESS | Stop managing a resourceDeletes the record from state while the remote object keeps existing; the next plan proposes creating it again. |
terraform state rm -dry-run ADDRESS | Preview a state removalNames the instances that match the address without forgetting any of them. |
terraform state push PATH | Upload a local state fileWrites the file to the configured backend once lineage and serial checks pass; a path of - reads from stdin. |
terraform state push -force PATH | Push state past safety checksOverrides the lineage and serial-number checks, so the destination state is overwritten; not recommended. |
terraform state replace-provider FROM_PROVIDER_FQN TO_PROVIDER_FQN | Change a provider's sourceRewrites every resource in state from one provider address to the other and always saves a backup first. |
terraform force-unlock LOCK_ID | Release a stuck state lockRemoves the lock with that ID from the state of the current configuration; infrastructure is not modified. |
terraform force-unlock -force LOCK_ID | Unlock without confirmationSkips the question that normally confirms the unlock. |
terraform taint ADDRESS | Mark a resource as taintedDeprecated in favour of apply -replace; the next plan proposes replacing the tainted object. |
terraform untaint ADDRESS | Remove the tainted markerEdits only the state, for an object flagged as damaged that turned out to work correctly. |
Importing existing infrastructure 7
| Command | What it does |
|---|---|
terraform import ADDRESS ID | Import an existing resourceBinds the remote object with that provider-specific ID to a resource address in state; import each object only once. |
terraform import module.foo.aws_instance.bar i-abcd1234 | Import into a moduleExample that places an EC2 instance in resource bar inside the module named foo. |
terraform import 'aws_instance.baz[0]' i-abcd1234 | Import into a count instanceExample that targets the first instance of a resource configured with count. |
terraform plan -generate-config-out=PATH | Generate config for import blocksExperimental: writes HCL for resources named in import blocks; the target has to be a file that is not there yet. |
terraform query | Search existing infrastructureRuns the list blocks in .tfquery.hcl files and prints the matching remote resources so they can be imported. |
terraform query -generate-config-out=PATH | Write import blocks for resultsSaves import and resource blocks for everything found; the target has to be a file that is not there yet. |
terraform query -json | Query results as JSONCombined with -generate-config-out, the generated configuration lands in the JSON rather than in a file. |
Workspaces 10
| Command | What it does |
|---|---|
terraform workspace | Workspace subcommand groupContainer for the new, list, show, select and delete subcommands. |
terraform workspace list | List workspacesAn asterisk marks the workspace that is currently selected. |
terraform workspace list -json | Workspace list as JSON |
terraform workspace show | Show the current workspace |
terraform workspace new NAME | Create a workspaceFails when a workspace with that name is already present. |
terraform workspace new -state=PATH NAME | New workspace from a state fileInitialises the fresh workspace with a copy of the state found at the given path. |
terraform workspace select NAME | Switch workspaceLater operations use the chosen workspace, which must already exist. |
terraform workspace select -or-create NAME | Select or create a workspaceMakes the workspace first when none of that name exists. |
terraform workspace delete NAME | Delete a workspaceRefused when the workspace is the current one or still tracks resources. |
terraform workspace delete -force NAME | Force-delete a workspaceDeletes even a workspace that tracks resources, which then live on unmanaged. |
Providers and modules 12
| Command | What it does |
|---|---|
terraform providers | Show required providersExplains where each provider requirement of the current configuration was detected. |
terraform providers lock | Update the dependency lock fileRecords provider versions and checksums from the origin registries without installing the providers. |
terraform providers lock -platform=windows_amd64 -platform=darwin_amd64 -platform=linux_amd64 | Lock checksums for several platformsPre-populates the lock file for Windows, macOS and Linux so runs on those systems add no further checksums. |
terraform providers lock -fs-mirror=DIR | Lock from a filesystem mirrorFor in-house providers: takes the packages from a local directory, not from their registry. |
terraform providers lock -net-mirror=URL | Lock from a network mirrorFetches package data from a mirror service at that base URL rather than the registry. |
terraform providers mirror TARGET-DIR | Mirror providers to a directoryDownloads every required provider into a local folder laid out as a filesystem mirror, for networks without registry access. |
terraform providers mirror -platform=OS_ARCH TARGET-DIR | Mirror for another platformOtherwise only packages for the machine running the command are fetched; repeat the flag per target system. |
terraform providers schema -json | Dump provider schemasPrints the detailed schemas of the providers the configuration uses; the -json flag is mandatory. |
terraform get | Download modulesFetches the modules declared in the root module into the .terraform subdirectory. |
terraform get -update | Update downloaded modulesModules that are already present are looked up again and replaced by newer releases where they exist. |
terraform modules | List declared modulesShows each module's key, source and version; needs Terraform v1.10.0 or later. |
terraform modules -json | Module list as JSON |
Testing and console 11
| Command | What it does |
|---|---|
terraform test | Run module testsExecutes the test files in the current directory and the tests directory; it creates real infrastructure, then tries to destroy it. |
terraform test -filter=TESTFILE | Run selected test filesLimits the run to the named file; repeat the option to add more files. |
terraform test -test-directory=PATH | Change the test directoryPoints the command at a folder other than the default, tests. |
terraform test -verbose | Show plan or state per runPrints the plan or the state of each run block while the tests execute. |
terraform test -json | Test results as JSON |
terraform test -junit-xml=PATH | Write a JUnit XML reportStores the report at a relative or absolute path; it cannot be combined with -cloud-run. |
terraform test -cloud-run=SOURCE | Run tests on HCP TerraformExecutes remotely for a module from a private registry, named by its source address. |
terraform console | Open the expression consoleInteractive prompt for trying expressions and functions against the current state; type exit to leave. |
terraform console -plan | Console against a new planEvaluates expressions against the planned state, to inspect changes that are not applied yet. |
terraform console -scope='module.child' | Console inside a child moduleMoves the evaluation scope from the root module to the module address given. |
echo 'split(",", "foo,bar,baz")' | terraform console | Evaluate an expression from a scriptPipes newline-separated expressions into the console; only the result of the last one is printed. |
Automation and environment variables 17
Arguments from TF_CLI_ARGS are inserted after the subcommand and before the flags typed on the command line, so the typed flags take precedence.
| Command | What it does |
|---|---|
terraform -chdir=DIR SUBCOMMAND | Run from another directoryGlobal option placed in front of the subcommand; Terraform then reads and writes its files in DIR. |
terraform apply -input=false | Disable interactive promptsBlocks the approval prompt as well, so apply fails unless approval comes another way. |
terraform apply -json | Stream apply output as JSONEmits one JSON message per line and needs -auto-approve or a saved plan. |
terraform plan -detailed-exitcode | Exit code reports pending changesExit status 0 means no changes, 1 an error and 2 that the plan contains changes. |
terraform plan -no-color | Disable coloured outputFor logs and systems that cannot render terminal formatting sequences. |
export TF_LOG=trace | Enable debug loggingSends detailed logs to stderr; unset the variable or set it to off to stop. |
export TF_LOG_PATH=./terraform.log | Write logs to a fileOnly takes effect while TF_LOG is switched on too. |
export TF_INPUT=0 | Disable prompts everywhereMakes every command behave as though -input=false had been passed; the value false works too. |
TF_CLI_ARGS | Default arguments for all commandsIts value is inserted right after the subcommand, so flags typed on the command line still win. |
TF_CLI_ARGS_plan="-refresh=false" | Default arguments for one commandTF_CLI_ARGS_ plus a command name limits the extra arguments to that command, here plan. |
TF_DATA_DIR | Move the .terraform data directoryHas to be identical for every command from init onward, or providers and modules will not be found. |
export TF_WORKSPACE=your_workspace | Select a workspace by variableTakes the place of workspace select; recommended only for non-interactive runs. |
TF_IN_AUTOMATION | Mark a run as automatedOnce it holds a value, the output stops suggesting which command to run next; the change is cosmetic. |
export TF_CLI_CONFIG_FILE="$HOME/.terraformrc-custom" | Use another CLI config fileSupersedes TERRAFORM_CONFIG, an older name that is now deprecated. |
TF_PLUGIN_CACHE_DIR | Set the provider plugin cacheDoes the same job as plugin_cache_dir in the CLI configuration file, without editing that file. |
export TF_REGISTRY_CLIENT_TIMEOUT=15 | Raise the registry timeoutRequests to the remote registry normally time out after 10 seconds. |
CHECKPOINT_DISABLE | Turn off update checksOnce set, Terraform no longer asks HashiCorp Checkpoint about new versions and security bulletins. |
Help, version and login 12
| Command | What it does |
|---|---|
terraform -help | List all commandsPrints the main workflow commands first, then the rest, followed by the global options. |
terraform validate -help | Help for one subcommandAdding -help to any subcommand prints its usage and options; validate is the example here. |
terraform -version | Print the versionA global option that does the same as the version subcommand. |
terraform version | Show Terraform and provider versionsAlso names the platform and reports the upgrade and security check unless that check is disabled. |
terraform version -json | Version details as JSONThe JSON object leaves out upgrade and security information. |
terraform -install-autocomplete | Install shell tab completionAdds completion for command names to the bash or zsh profile; restart the shell afterwards. |
terraform -uninstall-autocomplete | Remove shell tab completionTakes the completion hook out of the shell profile, provided it was not edited by hand. |
terraform login | Sign in to HCP TerraformOpens a browser to obtain an API token for app.terraform.io and stores it locally; interactive use only. |
terraform login HOSTNAME | Log in to another hostFor Terraform Enterprise or any other host that offers Terraform services. |
terraform logout | Remove saved credentialsDeletes the token from local storage only; it stays valid on the server until revoked. |
terraform metadata functions -json | List function signaturesPrints a JSON description of every function the Terraform language offers. |
terraform stacks | Manage Terraform StacksEntry point for the Stacks commands, among them init, validate, create and list. |
No row on this page matches that filter.
Notes
The loop
terraform init downloads providers and modules and configures the backend; run it after cloning and after adding a provider. terraform fmt and terraform validate tidy and type-check the configuration without touching infrastructure, and belong in CI. terraform plan computes the changes and prints them — read every line, because a resource marked for replacement is destroyed and created again — and terraform apply executes them after a confirmation; plan -out=file then apply file guarantees the applied change is the one reviewed. terraform destroy removes everything the configuration manages.
State
The state file maps configuration to real resources. terraform state list shows what Terraform believes it manages, and state show prints one resource's attributes. terraform import ADDRESS ID brings an existing resource under management by adding it to state — write the configuration block first, import, then plan until the diff is empty; an import block in the configuration does the same job during plan and apply. terraform output prints output values, with -json for scripts. Never edit the state file by hand; use the state subcommands, which write a backup before they change anything.
Workspaces and remote state
terraform workspace list shows workspaces, which give one configuration several independent states (dev, staging, prod) in the same backend; workspace select switches. For a team, a remote backend with locking (S3 with its lock file, HCP Terraform, GCS) is the first thing to configure, because two people applying against local state is how resources get orphaned. The older DynamoDB-based locking of the S3 backend is deprecated.
Questions
What is the Terraform workflow?
The basic workflow is: terraform init (initialize) → terraform plan (preview) → terraform apply (execute) → terraform destroy (cleanup).
What does terraform plan do?
terraform plan creates an execution plan showing what changes will be made to your infrastructure without actually applying them.
How do I import existing resources into Terraform?
Write the resource block, then run terraform import ADDRESS ID, where ID is the identifier the provider expects, such as an EC2 instance ID. An import block in the configuration does the same during plan and apply, and terraform plan -generate-config-out=PATH can draft the resource block for it.
How do I format Terraform files?
terraform fmt rewrites the configuration files in the current directory to the canonical style. Add terraform fmt -recursive to include subdirectories, or run terraform fmt -check in CI, which changes nothing and exits non-zero when a file needs formatting.
What replaced terraform taint and terraform refresh?
Both commands are deprecated. Instead of taint, run apply with the -replace option, for example terraform apply -replace="aws_instance.example[0]". Instead of refresh, run terraform apply -refresh-only, which shows the detected changes and asks before writing them to the state.
How do I make sure apply runs exactly the plan I reviewed?
Save the plan with terraform plan -out=PATH, read it with terraform show FILE, then give the same file to apply (terraform apply PLAN). A saved plan is applied without a confirmation prompt, and no further planning options can be added at that point.
Sources and checks
- HashiCorp Developer, Terraform v1.16.x documentation: terraform init command reference Usage line, options and examples
- Terraform 1.16.5 built-in help: output of "terraform -help" and "terraform SUBCOMMAND -help" from the official Linux release binary Usage lines and option lists of every subcommand
- HashiCorp Developer, Terraform v1.16.x documentation: terraform plan command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform apply command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform destroy command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform refresh command reference Usage line, options and examples
38 more source pages
- HashiCorp Developer, Terraform v1.16.x documentation: Terraform CLI environment variables reference TF_LOG, TF_VAR_name, TF_CLI_ARGS and the other environment variables
- HashiCorp Developer, Terraform v1.16.x documentation: terraform taint command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform fmt command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform validate command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform show command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform output command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform state list command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform state show command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform state pull command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform graph command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform state command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform state mv command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform state rm command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform state push command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform state replace-provider command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform force-unlock command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform untaint command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform import command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform query command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform workspace command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform workspace list command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform workspace show command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform workspace new command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform workspace select command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform workspace delete command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform providers command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform providers lock command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform providers mirror command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform get command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform modules command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform test command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform console command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: Machine-readable UI output reference The -json output mode of plan, apply, refresh and test
- HashiCorp Developer, Terraform v1.16.x documentation: Terraform CLI overview Global options, per-command help, shell tab completion and the Checkpoint setting
- HashiCorp Developer, Terraform v1.16.x documentation: terraform version command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform login command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform logout command reference Usage line, options and examples
- HashiCorp Developer, Terraform v1.16.x documentation: terraform stacks command reference Usage line, options and examples
Every row on this page was matched to a line in the documentation above on . A binding that could not be found there is not listed.
Found a wrong or missing key? Tell us and it gets checked against the source. How we verify describes the process and its limits.