Terraform Best Practices
Terraform consultingTwitter @antonbabenkoTerraform Weekly
English
English
  • Welcome
  • Key concepts
  • Code structure
  • Code structure examples
    • Terragrunt
    • Terraform
      • Small-size infrastructure with Terraform
      • Medium-size infrastructure with Terraform
      • Large-size infrastructure with Terraform
  • Naming conventions
  • Code styling
  • FAQ
  • References
  • Writing Terraform configurations
  • Workshop
Powered by GitBook
On this page
  • What are the tools I should be aware of and consider using?
  • What are the solutions to dependency hell with modules?
Export as PDF

FAQ

FTP (Frequent Terraform Problems)

PreviousCode stylingNextReferences

Last updated 1 month ago

What are the tools I should be aware of and consider using?

  • - Orchestration tool

  • - Code linter

  • - Version manager

  • - A modern composable framework for Terraform backed by YAML

  • - HashiCorp plugin for the version manager

  • - Pull Request automation

  • - Collection of git hooks for Terraform to be used with

  • - Cloud cost estimates for Terraform in pull requests. Works with Terragrunt, Atlantis and pre-commit-terraform too.

What are the solutions to with modules?

Versions of resource and infrastructure modules should be specified. Providers should be configured outside of modules, but only in composition. Version of providers and Terraform can be locked also.

There is no master dependency management tool, but there are some tips to make dependency specifications less problematic. For example, can be used to automate dependency updates. Dependabot creates pull requests to keep your dependencies secure and up-to-date. Dependabot supports Terraform configurations.

Terragrunt
tflint
tfenv
Atmos
asdf-hashicorp
asdf
Atlantis
pre-commit-terraform
pre-commit framework
Infracost
dependency hell
Dependabot