Skip to main content
Examples/Stack Names
EXAMPLE

Stack Names

Name stacks imperatively with the `name` field — the explicit name always wins over filenames, templates, and patterns.

Stacks
Try it out View on GitHub
cloudposse / atmos

Try it out

Copy the example into a new directory and make it your own:

atmos init examples/stack-names
cd stack-names

Follow the README for prerequisites and next steps.

Initialization and repository settings

See it in action

RECORDED DEMO
stack-names
Recorded from this example
Real commands. Real output.
README.md1.6 KB
View on GitHub

Stack Names Example

This example demonstrates imperative stack naming using the name field in stack manifests.

Overview

Stack names are determined by the following precedence (highest to lowest):

  1. name - Explicit name from the stack manifest (always wins)
  2. name_template - Template-based naming (if configured)
  3. name_pattern - Pattern-based naming (if configured)
  4. Filename - Basename of the stack file (fallback)

This example demonstrates the name field, which always takes precedence over other naming methods.

Stacks

FileName FieldCanonical Name
stacks/dev.yaml(none)dev
stacks/prod.yamlproductionproduction

Usage

# List all stacks
atmos list stacks

# Dev stack - uses filename
atmos terraform plan mock -s dev

# Prod stack - uses explicit name
atmos terraform plan mock -s production

# This will NOT work (filename is not the canonical name):
# atmos terraform plan mock -s prod

Key Points

  • The name field takes precedence over the filename
  • Only the canonical name is valid for the -s flag
  • This is useful for migrations, legacy infrastructure, or matching existing Terraform workspace names