Terraform Associate 004Demo

terraform fmt rewrites Terraform configuration files to the canonical Terraform format and style. By default, it scans and formats configuration files in the current directory; subdirectories require the -recursive option.

Terraform treats a managed resource that exists in state but no longer has a corresponding configuration block as a resource to destroy. Applying the resulting plan deletes the virtual machine.

A Terraform output block must include a value expression, which Terraform evaluates and exposes as the output value. description and sensitive are optional, and default is not an output-block argument.

Terraform references a data-source attribute with data.<TYPE>.<NAME>.<ATTRIBUTE>. Therefore, the id of the aws_ami data source named web is data.aws_ami.web.id.

terraform init -upgrade upgrades previously selected provider plugins to the newest versions allowed by the configuration’s version constraints, updating the dependency selections in the lock file as applicable.

Terraform CLI displays root-module output values. A child module’s output is available to its parent through module.<module_name>.<output_name>, so the root configuration must define an output block that references that child output in order for it to be printed.

Managed resource attributes in HCL use the reference syntax <resource_type>.<resource_name>.<attribute>. Therefore, the name attribute is referenced as kubernetes_namespace.example.name.

HCP Terraform workspaces can run Terraform remotely on HashiCorp-managed execution environments, retain historical state versions and a history of runs, and use variable sets to apply Terraform and environment variables across workspaces. Terraform Community Edition is multi-provider and can store configuration in a VCS, but those are not HCP-workspace-exclusive capabilities. HCP Terraform workspaces Remote operations in HCP Terraform

HCP Terraform uses team-based access control. Permissions can be granted to teams at the project and workspace scopes, including the ability to plan or apply runs. Assigning each organizational team access only to its own projects or workspaces enforces ownership boundaries and prevents unauthorized applies to another team’s infrastructure.

Terraform data-source attributes use the data.<TYPE>.<NAME>.<ATTRIBUTE> reference form. Interpolating data.azurerm_resource_group.example.name into a string template and appending -vnet yields the required virtual-network name. Terraform’s join function requires a separator and a single list of strings, while concat combines sequence values rather than individual string fragments.

A Terraform data block queries an existing provider resource and makes its attributes, including its ID, available for reference in the configuration without creating or managing that resource.

Terraform enables detailed diagnostic logs through the TF_LOG environment variable; setting it to a verbosity level such as TRACE outputs logs to standard error during the Terraform run.

Terraform input variables that have no default value are required. A child module receives required input-variable values through arguments in the calling configuration’s module block.

Terraform providers are plugins that expose resource types and communicate with cloud-provider and other service APIs. They enable Terraform to provision resources on both cloud and self-hosted/on-premises infrastructure platforms. HashiCorp documents that providers interact with cloud providers, SaaS providers, and other APIs, and that their resource types can be provisioned on cloud or on-premises platforms.

Terraform must initialize a working directory with terraform init to configure and begin using its backend, including a cloud backend.

Marking a Terraform variable as sensitive suppresses or redacts its value in Terraform’s human-readable output, but it does not prevent that value from being recorded in state when required. State must be protected as sensitive data.

terraform init prepares an existing Terraform working directory, including initializing the backend and installing required providers and modules. It does not create an example main.tf configuration file.

A Terraform configuration’s working directory must be initialized with terraform init before provisioning operations. terraform init prepares the directory, including backend setup and provider/module installation; terraform apply then creates the infrastructure described by the configuration. Initialize the Terraform working directory

A validation block nested in a variable block defines a condition the input value must satisfy. If that condition evaluates to false, Terraform reports the configured error and stops the operation. HashiCorp Terraform variable block reference

A Terraform map(string) represents a collection of values identified by string keys, with every value constrained to a string. This matches resource tags, which are arbitrary key-value pairs such as Environment = "prod".

Terraform automatically creates and manages the .terraform directory during initialization to store cached provider plugins and modules, along with workspace and backend-related metadata. Terraform state is stored separately, either in a local state file or in the configured backend.

Infrastructure configuration should remain under version control and be changed through a reviewed pull request. HCP Terraform can run speculative plans for pull requests and initiates a run after the change is merged, preserving review, auditability, and the repository as the source of truth. Direct cloud-side changes can create configuration drift.

Terraform detects configuration drift caused by resources deleted outside its workflow and creates the missing managed instances so that the real infrastructure again matches the Terraform configuration. Unaffected resources that already match the configuration are not rebuilt.

Refresh-only mode updates Terraform state and root-module outputs to reflect changes made to remote objects outside Terraform. It queries the provider using its configured authentication and compares the provider-reported remote objects with the existing state; it does not plan changes to make infrastructure match resource definitions in Terraform configuration.