Terragrunt is a mature, production-grade Infrastructure as Code orchestration CLI tool that wraps OpenTofu and Terraform. Its core function is to manage the lifecycle of IaC modules across environments: it parses HCL configuration (`terragrunt.hcl`, stacks), discovers units and stacks in a file tree, resolves inter-module dependencies, executes OpenTofu/Terraform commands with automatic remote state backend management (S3, GCS, Azure), and caches provider downloads and module sources via a content-addressable store (CAS). The architecture is a monolith with a rich CLI surface (over 20 subcommands including `run`, `catalog`, `browse`, `scaffold`, `find`, `list`, `render`, `hcl fmt`, `dag graph`, etc.) and a custom implementation of the CLI framework (`internal/clihelper`). It features a Bubbletea-based TUI for catalog browsing and an extensible filter engine for selecting units by path, attributes, or git changes. The codebase is heavily test-covered (unit, integration, fuzz) and actively maintained by Gruntwork. Key reusable patterns include virtual abstractions for filesystem, execution, and HTTP; a generic concurrent cache; a strict controls system for deprecation gating; and a content-addressable git store for deduplicating source downloads.
This repository provides a comprehensive suite of GitHub Actions for automating Terraform and OpenTofu workflows in CI/CD pipelines. Each action (e.g., terraform-apply, terraform-plan, terraform-validate) is implemented as a standalone reusable workflow with standardized inputs, outputs, and Docker-based execution environments. The architecture features a common shell library (actions.sh) that handles tool installation, backend initialization, and shared utilities, while individual actions focus on specific operations like plan generation, state management, or pull request commenting. Key capabilities include version detection from multiple sources, backend fingerprinting for state identification, automated PR commenting with approval workflows, and support for both Terraform and OpenTofu. The project emphasizes reliability through extensive testing across versions and backends, with clear separation of concerns between action definitions, implementation logic, and documentation generation.
This repository implements a Terraform provider for managing Incus, a container and virtual machine orchestration platform. It provides full CRUD operations for Incus resources such as instances, networks, storage pools, profiles, projects, certificates, cluster groups, and server configuration, along with corresponding data sources for reading existing state. The provider is built using the Terraform Plugin Framework (v1.19.0) with some fallback to Plugin SDK v2, and communicates with Incus via its client library (github.com/lxc/incus/v7). Key entry points include the main.go provider server, internal/provider/provider.go for resource registration, and individual resource files under internal/{certificate,cluster,image,instance,network,profile,project,server,storage}. The provider supports multiple remotes, OIDC authentication, clustering, and PKI, and includes a code generation tool (cmd/generate-datasources) that produces consistent data source implementations and documentation from a YAML configuration and Go templates. Acceptance tests require a live Incus environment and cover complex scenarios like instance lifecycle, exec triggers, file uploads, and import. The codebase is well-structured with shared utilities in internal/common for config/device/file/import handling, and demonstrates a consistent pattern for state synchronization and error handling. However, it carries some technical debt from its fork of the LXD provider, including dual SDK usage and heavy boilerplate that could benefit from further abstraction.
Digger (now OpenTaco) is an infrastructure-as-code orchestration platform that automates Terraform, OpenTofu, Terragrunt, and Pulumi workflows within existing CI/CD pipelines. The system provides PR-level automation (plan/apply comments), drift detection, policy-as-code via OPA, and an optional Terraform Enterprise-compatible state management and remote execution layer. It integrates with GitHub, GitLab, Bitbucket, Azure DevOps, and Buildkite through webhooks and CI backends. The architecture is a multi-service monorepo: a Go backend (Gin/GORM) handles webhooks, job scheduling, and a web UI; a separate CLI tool (cobra) runs directly in CI; a drift detection service with cron scheduling; a sandbox sidecar (TypeScript/Node) for remote execution; and the Taco service (Echo) that reimplements TFE APIs for state management, RBAC, and run execution. The UI is a React/TanStack Router app with WorkOS authentication. The codebase is actively maintained with frequent releases, extensive SQL migrations, Helm charts for Kubernetes deployment, and dual open-core and enterprise (ee/) feature sets.
This repository is a curated 'awesome list' of OpenTofu resources, tools, and community links. It is not a software application or data pipeline; it is a static markdown document (README.md) that aggregates official OpenTofu links, community channels, feature highlights, tools (environment managers, wrappers, CI, tests, state management, providers, platforms, registries, helpers), learning materials, media, and podcasts. The repository includes standard awesome list infrastructure: a Jekyll-based GitHub Pages site (with custom CSS and a CNAME for awesome-opentofu.com), CI workflows for link checking and markdown linting, and a contribution guide. There is no executable code, no API, no data transformations. The value lies in the curated, up-to-date collection of external resources, not in any software logic. The repo is actively maintained with recent commits and automated dependency updates via Renovate and Dependabot.