Stack configuration: imports, inheritance, deep merging, locals, vars, settings, metadata, overrides
Stacks are YAML configuration files that define which components to deploy, with what settings, and how they relate to each other. They separate configuration from infrastructure code, enabling the same Terraform root modules to be deployed across many environments with different settings.
A stack manifest is a YAML file that declares components and their configuration for a specific combination of organization, tenant, account, region, and stage. Atmos discovers stack manifests based on included_paths and excluded_paths in atmos.yaml, then deep-merges all imported configurations to produce the final resolved state for each component.
Stacks are not Terraform workspaces, although Atmos derives workspace names from stack names. A single stack manifest can configure multiple components, and a single component can appear across many stacks with different variable values.
Atmos discovers stack manifests based on included_paths and configured in the section
of . For the complete configuration reference, see the skill.
excluded_pathsstacksatmos.yamlatmos.yamlatmos-configAtmos resolves the stack name using this priority (highest first):
name field in the stack manifest (explicit override).name_template in atmos.yaml (Go template).name_pattern in atmos.yaml (token pattern).prod.yaml becomes prod).A stack manifest can contain the following top-level sections:
# Optional: explicit stack name override