Skip to main content

atmos aws cloudformation get template

Print the deployed stack’s template. By default, Atmos retrieves the processed template and formats it as YAML. Use --original to retrieve the submitted body.

Experimental
CloudFormation Configuration

Configure templates, parameters, and delivery targets for your component.

atmos aws cloudformation get template --help

Usage​

atmos aws cloudformation get template <component> --stack <stack> [options]

Examples​

atmos aws cloudformation get template vpc -s plat-ue2-dev

Fetch the original, user-submitted template instead of the processed one:

atmos aws cloudformation get template vpc -s plat-ue2-dev --original

By default the template is re-serialized as pretty-printed YAML, because CloudFormation often stores the processed template as JSON. With --original, Atmos prints the body exactly as CloudFormation returned it, byte for byte, with comments, quoting, and key order intact, so you can diff it against your source file:

atmos aws cloudformation get template vpc -s plat-ue2-dev --original > deployed.yaml
diff template.yaml deployed.yaml

A stack that does not exist is an error that points at atmos aws cloudformation apply.

Arguments​

component (required unless selecting multiple components)
CloudFormation component name in the Atmos stack.

Flags​

--stack, -s (required for a single component)
Atmos stack. With bulk selection flags, limits the selected components to this stack.
--original (optional)
Fetch the user-submitted template instead of the processed one CloudFormation deployed, and print it exactly as returned, without re-serializing it.
--all (optional)
Process all aws/cloudformation components. Deployment runs dependencies first; deletion runs consumers first.
--affected (optional)
Process affected aws/cloudformation components and their dependencies. Compares the working tree against a base: see --base and the Git flags below.
--include-dependents (optional)
With --affected, include dependent aws/cloudformation components.
--base (optional)
Git base ref or SHA to compare against for affected detection: --base=origin/main. A value that looks like a commit SHA is treated as --sha, anything else as --ref. Used with --affected.
--tags (optional)
Filter by tags (comma-separated, matches any): --tags=production,tier-1. Composes with --all/--affected to narrow the selected set further; cannot be combined with a single component argument.
--labels (optional)
Filter by labels (repeatable and/or comma-separated key=value or key:value pairs, matches all): --labels=cost-center=platform,compliance=sox. Composes with --all/--affected/--tags; cannot be combined with a single component argument.
--ci (optional)
Enable CI integration for supported operations when ci.enabled is configured. Summary and output-variable publishing use their respective CI settings. Also enabled by CI and ATMOS_CI.
--ref (optional)
Git ref to compare against for affected detection. Used with --affected.
--sha (optional)
Git SHA to compare against for affected detection. Used with --affected.
--repo-path (optional)
Path to an already cloned target repository to use as the affected baseline. Used with --affected.
--clone-target-ref (optional)
Clone the target ref instead of checking it out in the current repository for affected detection. Used with --affected.
--ssh-key (optional)
Path to the SSH private key used to clone the target ref for affected detection. Used with --clone-target-ref.
--ssh-key-password (optional)
Password for the SSH private key used to clone the target ref for affected detection. Used with --clone-target-ref.

This command does not fire lifecycle hooks.