A CLI tool that automatically generates Atlantis configuration for Terragrunt projects by analyzing dependencies.
Terragrunt Atlantis Config is a CLI tool that automatically generates Atlantis configuration files for Terragrunt projects. It solves the problem of manually maintaining Atlantis YAML configs in complex Terragrunt monorepos by analyzing dependency blocks and constructing a dependency graph to produce accurate, dynamic configurations.
DevOps engineers and platform teams managing Terraform infrastructure with Terragrunt in monorepos, especially those using Atlantis for pull request automation.
It eliminates the manual effort of writing and updating Atlantis configs, ensures dependency accuracy, and integrates seamlessly as a pre-workflow hook, making infrastructure changes more efficient and less error-prone.
Generate Atlantis config for Terragrunt projects.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Analyzes terragrunt.hcl files to build a Directed Acyclic Graph, ensuring accurate Atlantis configs without manual YAML maintenance, as described in the 'What is this?' section.
Designed to run as an Atlantis pre-workflow hook, dynamically generating configs after each repo clone, with clear setup examples in the 'Integrate into your Atlantis Server' section.
Supports extra_atlantis_dependencies locals for non-Terragrunt files like Dockerfiles, allowing triggers beyond standard HCL changes, as detailed in the 'Extra dependencies' section.
Enables parallel plan and apply in Atlantis using --parallel and --create-workspace flags, improving workflow efficiency, though it notes increased resource consumption in the 'Separate workspace' section.
Requires installing the tool on the Atlantis server and configuring pre-workflow hooks, involving additional steps like Packer provisioning, which adds operational overhead compared to static configs.
Enabling parallel workspaces with --create-workspace can significantly increase CPU, memory, and disk usage, as each workspace is cloned separately by Atlantis, per the 'Separate workspace' warning.
Tightly coupled with Terragrunt; any changes in Terragrunt's syntax or features could break compatibility, and it's useless for projects not using Terragrunt or Atlantis.