Terraform variables and outputs that set the "description" argument will store that description in the state file.
Terraform variables and outputs that set the "description" argument will store that description in the state file.
The description argument for Terraform variables and outputs is used to provide human-readable documentation for users of the Terraform configuration. It is not included in the state file. The state file is designed to store the current state of the managed infrastructure, including values of variables and outputs, but it does not retain descriptive metadata.
Terraform variables and outputs that set the "description" argument are not stored in the state file. The "description" argument is used to provide a human-readable description of the variable or output, and it is intended to be used as documentation for other users of the Terraform code. The state file is used to store the current state of the infrastructure managed by Terraform, including the values of variables and outputs. However, the "description" argument is not part of the state file, and it is not used by Terraform to manage the infrastructure. Instead, it is only used as metadata to describe the variable or output.
Answer is B. Descriptions aren't stored in the state file.
1) Create the following Terraform configuration: provider "aws" { region = "eu-west-1" } variable "instance_type" { description = "The type of instance to create" default = "t2.micro" } resource "aws_instance" "example" { ami = "ami-096800910c1b781ba" # Replace this with an appropriate AMI ID for your region instance_type = var.instance_type } output "instance_id" { description = "The ID of the created instance" value = aws_instance.example.id } 2) After you run terraform apply on this configuration, the state file (terraform.tfstate) will include the value of the instance_type variable ("t2.micro") and the value of the instance_id output (which would be the ID of the created AWS instance), but it would not include the descriptions of either the variable or the output.
Should be B. Tested this - no any descriptions v 1.2.7
I checked in my LAB. terraform.tfstate file doesnot store descriptions
Terraform state files are intended to store the actual configuration and state of the infrastructure, focusing on information that is necessary for Terraform to understand and manage the resources. Descriptions, being informational and not affecting the infrastructure's configuration or behavior, are typically not included in the state file to keep it concise and focused on essential details for Terraform's management.
B, tested on my lab, state only stores resources information it does not store outputs or variables
Tested now.. Outputs are present in state file but description is not: { "version": 4, "terraform_version": "1.3.7", "serial": 19, "lineage": "8de81937-55d8-2487-7ad0-cabba43e4403", "outputs": { "iam_assumed_role": { "value": "user_iam_assumed_role", "type": "string" }, "user_role_to_assume": { "value": "arn:aws:iam::999999999:role/user_iam_assumed_role", "type": "string" } }, "resources": [ { }
The correct answer is B.
Validated; it would just show type, value in the terraform state.
it isn't in the state, just check it
Vaoted B.
Description not in state file
Answer is A, I can see description in state file on my environment
no you cannot
The answer is B. Descriptions aren't stored in the state file.
Correct Ans is B
B is correct
i think B
B. False
Answer is B
variables are not stored in state
simply check the output of "terraform state pull" or see inside the tfstate file if using local state, there are no descriptions stored in the state
I don't understand how such a simple question can show the wrong answer by the website.
A. True Terraform variables and outputs that set the "description" argument will indeed store that description in the state file. This allows for better documentation and understanding of the purpose of variables and outputs within the Terraform configuration. However, it's important to note that sensitive information should not be included in descriptions as the state file is stored in plain text and could potentially expose sensitive information if not handled properly.
not true. Terraform state file only stores the actual infrastructure resources and their state