14 docs tagged with "Terraform"

This Github Action is used to run Terraform apply for a single, Atmos-supported component with a saved planfile in S3 and DynamoDB.

This Github Action is used to detect drift

This Github Action is used to remediate drift

This Github Action is used to run Terraform plan for a single, Atmos-supported component and save the given planfile to S3 and DynamoDB.

GitHub Action that outputs list of Atmos components by jq query

When to use count and when to use for_each in Terraform

Details about computed values can cause `terraform plan` to fail

HCL is HashiCorp's configuration language used in multiple products, but most notably in `terraform`.

Infrastructure as Code (IaC) is the process of managing/provisioning Infrastructure as a Service (IaaS) using machine-readable definition files (usually DSLs), rather than rely on humans doing physical/manual hardware configuration.

Our opinionated best-practices for Terraform

Deep dive into Terraform implementation details and pitfalls

Every Terraform configuration has at least one module, known as its root module, which consists of the resources defined in the `.tf` files in the main working directory. Root modules are the terraform configuration that we actually **apply** and have terraform state.

Some helpful hints for Terraform

The many tools that make up the SweetOps approach