tg-migrate-populate

Populates Terragrunt environment configurations with real values replacing placeholder entries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating legacy Terraform environments to a new Terragrunt structure leaves scaffolded files full of PLACEHOLDER values that must be manually replaced with real resource names, IDs, and secrets mappings, which is tedious and error-prone across many environments. ## Core Features & Use Cases - Placeholder Replacement: Replaces PLACEHOLDER entries in terragrunt.hcl files with real Azure resource names, resource groups, and configurations sourced from legacy environment.auto.tfvars, backend.hcl, and secrets.tfvars.tmpl files. - State-Aware Orchestration: Verifies Phase 2 scaffolding is complete via migration_get_state before proceeding, and marks the environment as populated via migration_update_state afterward. - Residual Placeholder Detection: Scans populated environment directories for any remaining PLACEHOLDER strings and reports them for manual input. - Use Case: After scaffolding 13 standard environments, run this phase per environment (e.g., us-centralus-dev, uk-uksouth-prod) to inject real values, review the diffs, and confirm before moving to the next environment. ## Quick Start Populate the us-centralus-dev environment in my target repo with real values from the legacy Terraform configuration.

Frequently Asked Questions about tg-migrate-populate

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

FAQPage Schema
How do I replace placeholder values in Terragrunt migration files?

Run the populate phase with the target repo path and environment key. It reads legacy environment.auto.tfvars, backend.hcl, and secrets.tfvars.tmpl files, then replaces __PLACEHOLDER__ entries with real resource names, IDs, and configurations.

What sources provide real values for Terragrunt environment migration?

Resource names come from legacy environment.auto.tfvars or the Azure portal, tfstate config from legacy backend.hcl, and secrets from secrets.tfvars.tmpl get_env() mappings. The is_secondary flag is true for eastus2 and ukwest regions.

Can I populate an environment before the scaffold phase completes?

No. The skill checks migration state with migration_get_state first and requires Phase 2 scaffolding to be complete before populating. This ensures the target directory structure exists before values are injected.

What happens if placeholders remain after populating a Terragrunt environment?

The skill searches the populated environment directories for any remaining __PLACEHOLDER__ strings and reports them as needing manual input. It then presents a summary of replacements and key file diffs for review.

How many environments does the Terragrunt migration populate?

The populate phase runs once per environment across 13 standard environments, each identified by an env_key such as us-centralus-dev or uk-uksouth-prod. Each environment is marked populated in migration state after completion.