Gain insights into Infrastructure as Code with Terraform, sharpen your skills, and prepare for the HashiCorp Terraform Associate certification in a cloud-agnostic way.

HashiCorp Terraform Certified Associate Preparation Guide.png

Terraform_e.tar.gz

access_key_id

secret_access_key

init

validate

config

needed-copy

not-needed-copy

needed-copy-copy

This course is designed to help learners obtain the Terraform Associate certification from HashiCorp. 

You’ve likely picked up this course because you dabbled in Terraform as a hobbyist or in a
development environment, and you’re excited about the possibilities of deploying Infrastructure 
as Code (IaC). It will enable you to sharpen your skills and prove your knowledge with a certification from HashiCorp. Terraform is an amazing tool to deploy Infrastructure as Code in a cloud-agnostic way. We’re excited to share our accumulated knowledge with you through this course.

HashiCorp Terraform Certified Associate Preparation Guide

# What is a state in terraform?

The state maintained by Terraform is a JSON document stored locally or on a remote backend. Making direct edits to the file is highly discouraged. There are some occasions where we need to directly interact with the Terraform state, and in those cases, we use the `terraform state` command and its subcommands to assist us.



## The `terraform state` subcommands

Below is a list of `terraform state` subcommands available for use.

+ The `list` subcommand lists resources in the state.
+ The `mv` subcommand moves an item in the state.
+ The `pull` subcommand pulls the current state and output to `stdout`.
+ The `push` subcommand updates the remote state from a local state file.
+ The `rm` subcommand removes instances from the state.
+ The `show` subcommand shows a resource in the state.

# Resource addressing

​​When using the `terraform state` command, we’re likely going to interact with specific resource instances defined in the state. They can be accessed by what HashiCorp calls **standard address syntax**, which can be thought of as the way we reference resources in our configuration file.

References to resources in the state include individual resource instances, like an `aws_instance`, or groups of resources created by `count` or `for_each` resource arguments or a module.

## Syntax
The basic syntax is `[module path][resource spec]`. Technically, all resource instances are contained
within a module. Instances defined directly in a configuration are part of the root module, which is
implicit when using *standard address syntax*.

The `resource_spec` component is the path to the instance in a given module. For example, a subnet defined by the Azure vnet module named `my-vnet` could be referred to by the path 
`module.my-vnet.azurerm_subnets.subnet[0]`.

More generally the form could be expressed as `module.module_name_label.resource_type.resource_-
name_label.resource_attribute[element]`. Nested child modules would simply extend the form
until the proper level is reached to refer to the resource instance.

# The `list` subcommand

The `terraform state list` command is used to list resources within a Terraform state.


Learn how to list resources within a Terraform state.

Introduction to the Course

Introduction to Infrastructure as Code

Basics of Terraform

Outside the Workflow: Using the Terraform CLI

Terraform Modules

Navigate Terraform Workflow

Implement and Maintain State

Read, Generate, and Modify Configuration

Understand Terraform Enterprise Capabilities

Conclusion

Listing Resources within Terraform State

What is a state in terraform?

The `terraform state` subcommands

Listing Resources within Terraform State

What is a state in terraform?

The terraform state subcommands

The `terraform state` subcommands