Atlantis now plans the stacks affected by a module or dependency change

Until now Atlantis only planned a stack when a file inside that stack’s own directory changed. A change to a shared module under terraform/modules, or to a stack that other stacks depend on, planned nothing, and you had to comment atlantis plan -d terraform/live/<environment>/<project> for every affected stack yourself.

Atlantis now works out which stacks a pull request affects from the Terragrunt dependency graph: a module change plans every stack that uses that module, and a change to a stack plans the stacks that depend on it as well. Stacks that Atlantis is not allowed to run (for example the EKS cluster and networking stacks, which are managed by another pipeline) stay out of the plan, as before.

What this means for you

• Nothing to configure. Open a pull request as usual; the plan comment lists every affected stack.
• Expect more stacks in a plan when you touch a widely used module. Each one is planned in turn, so a large fan-out takes longer.
• Planning a stack by hand still works: comment atlantis plan -d terraform/live/<environment>/<project> to plan or re-plan one stack. Use it when you want to force a plan, or on a repository where this feature is switched off.
• When you add a stack that reads SOPS-encrypted secrets, call sops_decrypt_file() inside inputs, not in locals. The guidance in your repository (AGENTS.md and .agents/) shows the pattern; a decrypt call in locals stops Atlantis from building the stack list for the whole repository (it falls back to the old behaviour and shows a failed pre_workflow_hook status on the pull request).