The description argument for input variables and output values is metadata intended for human operators and documentation generation. This information is used by Terraform to provide context in the command-line interface (e.g., when prompting for a variable) and is included in module documentation. However, this descriptive metadata is not stored within the Terraform state file. The state file's primary purpose is to map the configuration to remote resources, track resource attributes, and manage dependencies, not to store the descriptive text from the configuration files.

The statement is incorrect because the state file is a machine-readable mapping of resources, not a repository for the human-readable comments or descriptions present in the .tf configuration files. The absence of this metadata in the state file can be confirmed by inspecting the raw terraform.tfstate JSON file after an apply operation.

1. HashiCorp Terraform Documentation

"Input Variables - The description Argument": This source explains the function of the description argument for variables. It states

"This description is displayed to the user in the CLI when they are prompted for a value

and is also used to generate documentation for a module." It makes no mention of the description being stored in the state file.

Source: HashiCorp

Terraform Language Documentation

"Input Variables"

https://developer.hashicorp.com/terraform/language/values/variables#the-description-argument.

2. HashiCorp Terraform Documentation

"Output Values - The description Argument": This document details the description argument for outputs

noting its purpose for human readability. It states

"This description is included in the output of terraform output and can be used to generate documentation for a module." This confirms its role is for user-facing information

not for state management.

Source: HashiCorp

Terraform Language Documentation

"Output Values"

https://developer.hashicorp.com/terraform/language/values/outputs#the-description-argument.

3. HashiCorp Terraform Documentation

"Purpose of Terraform State": This page describes the contents and purpose of the state file. It specifies that state is used for "Mapping to the Real World

" "Metadata

" and "Performance." The metadata mentioned refers to resource dependencies and provider configurations

not descriptive text from variables or outputs. The document states the state file stores "bindings between objects in a remote system and the resource instances declared in your configuration."

Source: HashiCorp

Terraform Language Documentation

"State"

https://developer.hashicorp.com/terraform/language/state#purpose-of-terraform-state.