terragrunt

Plan, validate, and apply Terragrunt infrastructure changes for Kubernetes clusters.

1|Updated Apr 6, 2025
One-click install
npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill terragrunt-david-driscoll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terragrunt
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/terragrunt
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill terragrunt-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you plan, validate, and apply infrastructure changes for your homelab Kubernetes environment without breaking your workflow or making unsafe assumptions about cluster networking.

Core Features & Use Cases

  • Task-first Terragrunt workflow: Use the repository’s task tg:* commands to keep operations consistent and avoid running terragrunt/OpenTofu directly.
  • Inventory-safe machine changes: Add or modify machines by editing inventory.hcl and following a plan-first review process, with explicit warnings to verify MAC/IP values.
  • Units→stacks→modules clarity: Understand and work within the architecture where stacks compose units and units wrap Terraform/OpenTofu modules, including feature flags and config-driven inputs.
  • Guardrails for state and testing: Follow validation and checklist steps, and use safe patterns for state operations involving indexed resources.

Quick Start

Ask the AI: "Generate a safe validation and planning plan for my live cluster after updating inventory.hcl, and include exactly which task tg:* commands I should run."

Frequently Asked Questions about terragrunt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan and validate bare-metal Kubernetes infrastructure changes with Terragrunt?

To plan bare-metal Kubernetes infrastructure changes with Terragrunt, use the repository's `task tg:*` commands for fmt, validate, and plan workflows. This ensures operations remain consistent and avoids running terragrunt or OpenTofu directly.

What is the safest way to update inventory.hcl machines in a homelab Kubernetes cluster?

The safest way to update inventory.hcl machines is through a plan-first review process with explicit warnings to verify MAC and IP values. This prevents unsafe assumptions about cluster networking when modifying bare-metal infrastructure.

Can I use Terragrunt units and stacks to wrap OpenTofu modules directly?

Yes, Terragrunt units wrap Terraform or OpenTofu modules, and stacks compose units. This architecture supports config-driven inputs and feature flags, allowing controlled infrastructure deployment within your homelab environment.

Does Terragrunt require human approval before applying infrastructure changes?

Yes, Terragrunt requires a plan-first review with human approval for apply. This controlled application process ensures all infrastructure changes are validated through task tg commands before deployment to the live cluster.

What limitations exist when managing indexed resource state in Terragrunt?

When managing indexed resource state in Terragrunt, you must follow safe patterns for state operations and validation checklists. Direct terragrunt or OpenTofu commands should be avoided to maintain inventory safety and prevent workflow issues.