atmos terraform planfile

Carry a saved Terraform plan from a planning job to a later apply job. Store and retrieve planfiles so your pipeline can apply the same plan that was reviewed, even when the jobs run on different machines.

Experimental

Configure CI Integration

Learn how to configure CI/CD integration in your atmos.yaml, including setting up providers (like GitHub Actions), managing workflows, environment variables, and secrets for automated infrastructure pipelines.

CI Configuration Reference

Subcommands

delete

Delete Terraform plan files from the configured storage backend.

download

Download a Terraform plan file from the configured storage backend.

list

List Terraform plan files from the configured storage backend.

show

Show metadata for a Terraform plan file from the configured storage backend.

upload

Upload a Terraform plan file to the configured storage backend.

Storage Backends

Atmos supports multiple storage backends for planfiles:

local/dir

Store planfiles on the local filesystem. Useful for development and single-machine workflows.

Default path: .atmos/planfiles/

aws/s3

Store planfiles in Amazon S3. Ideal for team workflows and cross-region access.

Configure via ATMOS_PLANFILE_BUCKET and ATMOS_PLANFILE_PREFIX environment variables.

github/artifacts

Store planfiles as GitHub Actions artifacts. Perfect for GitHub-native CI/CD workflows.

Automatically detected when running in GitHub Actions.

Related

• CI Configuration - Configure CI integration in atmos.yaml
• atmos terraform plan - Generate plans that can be uploaded
• Native CI - CI/CD integration overview