Install terragrunt with Homebrew, chocolatey, MacPorts, Nix, pacman, scoop, winget, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• terragrunt

Project history

Terragrunt's public GitHub repository was created in May 2016. The project began as a thin wrapper around Terraform, but its current README describes it more broadly as a flexible orchestration tool that lets OpenTofu and Terraform infrastructure scale.

The official documentation and README place Terragrunt around the terragrunt.hcl configuration file, where users define reusable inputs, dependencies, includes, and execution behavior around otherwise native Terraform or OpenTofu code. Over time, that made the CLI a common companion for teams splitting infrastructure into many small units rather than one large state and root module.

Gruntwork's Road to Terragrunt 1.0 posts describe the project as having remained pre-1.0 for nearly eight years, then moving toward a stable command-line interface and file format. The same series introduced or stabilized larger-scale features such as Stacks, feature flags, run reports, a runner pool, and a redesigned documentation site before the 1.0 milestone.

Adoption history

Terragrunt became a package-manager staple because it sits directly in day-to-day Terraform workflows: developers install the CLI, keep terragrunt.hcl files beside infrastructure code, and call Terragrunt from local shells and CI pipelines. The input metadata shows packages across Homebrew, Chocolatey, MacPorts, Nix, Arch, Scoop, winget, and zypper.

Official repository metadata showed thousands of stars and more than a thousand forks by July 2026. Gruntwork's 1.0 release writing also frames the release as tested with real-world platform teams and intended to stabilize behavior for the existing community.

How it is used

Common usage is to run Terraform or OpenTofu operations through terragrunt so shared configuration, dependency ordering, remote-state conventions, and multi-unit execution are handled consistently.

In package-nerd workflows, Terragrunt is often pinned or installed alongside Terraform or OpenTofu through system package managers, dev shells, CI images, and version managers because it participates in both local commands and automated infrastructure deployment.

Why package nerds care

Terragrunt is one of the more significant Terraform-adjacent packages in Homebrew because it is not just a helper script: it is a cross-platform Go CLI with its own configuration language conventions, release stream, compatibility expectations, and surrounding ecosystem of docs and package-manager formulas.

Its 1.0 work is especially relevant to package maintainers because the official goal was to stabilize the CLI and file format, reducing churn for users who install Terragrunt from operating-system package repositories.

Timeline

• 2016: Public Terragrunt repository created under gruntwork-io.
• 2024: Gruntwork announced the Road to Terragrunt 1.0 and described a plan to stabilize CLI and file-format behavior.
• 2025: Terragrunt Stacks reached general availability in the v0.78.0 period according to Gruntwork's official Stacks update.
• 2026: Terragrunt 1.0 shipped after release-candidate testing and community feedback.

Related projects

• Terraform and OpenTofu are the IaC engines Terragrunt orchestrates.
• Gruntwork's broader infrastructure tooling and commercial support ecosystem surround the project.
• Terramate and terragrunt-atlantis-config occupy nearby Terraform orchestration and automation niches.

Sources

• Docs: https://terragrunt.gruntwork.io/docs
• Input package metadata: source_facts.package-manager
• README: https://github.com/gruntwork-io/terragrunt#readme
• Repository metadata: https://api.github.com/repos/gruntwork-io/terragrunt
• Road to 1.0: https://www.gruntwork.io/blog/the-road-to-terragrunt-1-0
• Stacks update: https://www.gruntwork.io/blog/the-road-to-1-0-terragrunt-stacks-feature-complete
• Terragrunt 1.0 release: https://www.gruntwork.io/blog/terragrunt-1-0-released