Terragrunt Command Builder

Terragrunt is a thin, popular wrapper around Terraform that keeps your modules DRY, manages remote state, handles locking and lets you run operations across many modules at once. But its command surface - a long list of flags such as --terragrunt-working-dir, --terragrunt-config, --terragrunt-source and --terragrunt-parallelism - is easy to mistype, especially inside CI pipelines where a single wrong flag breaks the build. The Terragrunt Command Builder assembles correct commands for you. Choose an action (plan, apply, destroy, the run-all family, run, validate-inputs or terragrunt-info), set the working directory, config path and module source, optionally tune parallelism, and the tool returns a fully formed, copy-pasteable command. Nothing is executed and nothing leaves your browser, so it is safe to experiment. This is ideal for engineers onboarding to Terragrunt, for writing runbooks, or for generating the exact incantation needed in a pull-request description or a CI step. The result is always valid for the selected action, with quoting handled for you. Because the tool validates inputs before building, you avoid the embarrassing failure of a half-formed command on a shared runner, and because the output is plain text you can pipe it, store it in a snippet manager, or paste it straight into a terminal. The tool also shows a small stats row after each build so you can sanity-check that the expected number of flags was included and the command is not unexpectedly long before you run it.

• Actions - plan, apply, destroy, plan-all, apply-all, destroy-all, run, validate-inputs and terragrunt-info.
• Working directory - --terragrunt-working-dir to target a specific module directory.
• Config path - --terragrunt-config to point at a custom terragrunt.hcl.
• Source override - --terragrunt-source to override the module source at runtime.
• Parallelism - --terragrunt-parallelism to control concurrency for run-all.
• Run wrapper - the run action wraps an arbitrary inner terraform command safely with quoting.
• Validation - the tool flags unknown actions and an empty run command.
• Parallelism check - parallelism is validated as a positive integer.
• Stats row - shows flag count and command length after each build.
• Export - copy to clipboard or download as a shell script.
• Offline - runs entirely in the browser, no execution.
• Consistent quoting - inner commands are quoted so they pass through verbatim.
• Zero config - no setup required, just open and build.
• Reproducible - identical inputs yield identical commands every time.

1. Pick the action - select plan, apply, destroy, a run-all variant, run, validate-inputs or terragrunt-info.
2. Enter the working directory - for example ./modules/app or ./live/prod.
3. Set the config path - only if you use a non-default terragrunt.hcl location.
4. Set the source override - optional, used to point at a different module source.
5. Tune parallelism - for run-all actions, set a positive integer to limit concurrency.
6. Provide the inner command - required only when the action is run.
7. Build the command - click Build command to generate the output.
8. Read the stats - confirm the flag count and length look right, and that no error appeared.
9. Export - copy or download the result for your terminal or pipeline.

Example - run-all apply across modules: with action apply-all, working dir ./live and parallelism 4, the tool emits terragrunt apply-all --terragrunt-working-dir=./live --terragrunt-parallelism=4. For a one-off, choose run with inner command plan -var region=us-east-1 and working dir ./modules/app to get terragrunt run --terragrunt-working-dir=./modules/app "plan -var region=us-east-1". The quotes are added automatically so the inner command is passed through verbatim, avoiding the common mistake of forgetting to quote multi-word commands. You can then drop the generated line into a Makefile target or a GitHub Actions step unchanged, which keeps human-written automation consistent with what the tool produced. When you omit a field, the corresponding flag is simply left out, so a minimal plan with only a working directory yields a clean terragrunt plan --terragrunt-working-dir=./modules/app with no empty flag noise.

• Correct flags - no need to memorise the syntax.
• Run-all concurrency - parallelism is tuned safely.
• Safe inner quoting - the run action quotes commands correctly.
• Fast CI snippets - generate pipeline commands in seconds.
• Private - fully offline, nothing is executed.
• Fewer mistakes - validation catches unknown actions early.
• Shareable output - copy a known-good command into chat or docs.
• Self-review aid - the stats row helps you catch missing flags before running.