tg-migrate-validate

Validates Terragrunt migrations by running plans and enforcing a zero-destruction gate.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill tg-migrate-validate-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tg-migrate-validate
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/terragrunt-migrate/skills/tg-migrate-validate
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill tg-migrate-validate-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating infrastructure to Terragrunt risks accidentally destroying existing resources if the state import is incomplete. This Skill validates the migration by running terragrunt plan across all services and blocking any plan that would destroy resources. ## Core Features & Use Cases - HCL Validation: Syntax-checks all generated Terragrunt configuration files and verifies structural integrity before planning. - Plan Execution: Runs terragrunt plan across every service in the target environment and captures add, change, and destroy counts. - Zero-Destruction Gate: Fails the migration if any resource would be destroyed, reporting the affected services and suggesting fixes such as re-importing state. - Use Case: After importing an environment's state in Phase 4, run this validation to confirm the plan shows zero destroys before considering the migration safe to proceed. ## Quick Start Run the validation phase on my migrated environment by passing the target repository path and environment key, for example: validate ./my-infra-repo prod.

Frequently Asked Questions about tg-migrate-validate

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

FAQPage Schema
How do I validate a Terragrunt migration before applying changes?

Run terragrunt plan across all services in the target environment and inspect the add, change, and destroy counts. This Skill automates that process and enforces a gate that fails if any resource would be destroyed.

What is a zero-destruction gate in Terraform or Terragrunt migrations?

A zero-destruction gate blocks a migration when the plan shows any resources being destroyed. It ensures the state import captured all existing infrastructure, since destroys usually indicate missing or incorrect imports.

Why does terragrunt plan show resources being destroyed after import?

Destroys after import typically mean the state import was incomplete or the generated configuration does not match the existing resources. Re-import the affected resources or adjust the configuration, then re-run the plan.

What plan results are acceptable during a Terragrunt migration?

Zero adds, changes, and destroys means the state matches exactly. Additions with no destroys are acceptable for new Terragrunt-managed resources, and changes without destroys usually indicate tag updates or drift.

Does this validation step apply changes to my infrastructure?

No. It only runs terragrunt plan, which is read-only, plus HCL syntax validation. No resources are created, modified, or destroyed during validation.