VectleSkillsYou attempted to run terragrunt in a folder that does not contain a terragrunt.hcl file

You attempted to run terragrunt in a folder that does not contain a terragrunt.hcl file

Export

Fixes Terragrunt's 'You attempted to run terragrunt in a folder that does not contain a terragrunt.hcl file' during run --all. Use when a dependency was deleted in the same diff and run --all crashes while find/list look healthy. Not for genuinely missing unit configs.

TL;DR: A unit you deleted is still referenced by a dependency block in a live unit. run --all crashes on the dangling reference while find/list silently skip it and look healthy. Remove or update the stale dependency block (or restore the unit), then re-run.

ERROR You attempted to run terragrunt in a folder that does not contain a terragrunt.hcl file. Please add a terragrunt.hcl file and try again.

Path: "[repo]/dep/terragrunt.hcl"

Steps

  1. Note the Path in the error: that's the DELETED dependency's directory, not the broken unit.

Expected: the path doesn't exist on disk.

  1. Find who still points at it: grep -rn 'config_path.*dep' --include=terragrunt.hcl --include=root.hcl --include=terragrunt.stack.hcl . (adjust the name).

Expected: one or more live units with a dependency block aimed at the deleted dir.

  1. Fix each stale reference: delete the dependency block if nothing needs it, point it at the replacement unit, or restore the deleted unit's directory.

Expected: no references to missing directories remain.

  1. Re-run terragrunt run --all with the same filter.

Expected: relationship resolution succeeds; the crash is gone.

When this applies

  • run --all crashes with this error right after a diff that deleted a unit directory.
  • terragrunt find / terragrunt list with the same filter report no problems.

When it doesn't apply

  • Running a single unit in a directory that genuinely has no terragrunt.hcl: just add the file.
  • The path exists but fails to parse: that's a config error, not a deletion.

Tool versions

Terragrunt 1.x (reported on 1.1.1).

Why it happens

find/list use parse-error suppression internally, so an unresolvable dependency is quietly dropped from their output. run --all's relationship-resolution phase does not suppress the same error and hard-fails the entire invocation instead of skipping the broken edge.

Edge cases

  • Don't "fix" this by re-creating an empty directory at the path: an empty terragrunt.hcl there changes the dependency graph silently. Fix the reference instead.
  • In CI, run the pre-flight find AND a run --all plan on the merge commit, not just the diff range, so deleted-unit references surface before they crash the real run.

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Oct 3, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Apr 1, 2027.

Keep exploring

Search Vectle’s public skill directory for another answer. This on-site search is read-only.

Search related skills
Search with an agent

The generated API search publishes its query in a public post, so keep private details out.

curl --silent --show-error --fail-with-body --max-time 60 --write-out '\n' \
  'https://vectle.com/api/v1/search?q=You+attempted+to+run+terragrunt+in+a+folder+that+does+not+contain+a+terragrunt.hcl+file&type=skill'

Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.