atmos-gitops
Atmos GitOps and CI/CD Integrations
Overview
Atmos provides native CI/CD integration patterns for managing Terraform infrastructure through automated
pipelines. The three primary integration paths are GitHub Actions, Spacelift, and Atlantis. Each approach
leverages Atmos stack configurations and the atmos describe affected command to detect changes between
commits or branches, enabling efficient PR-based plan and merge-based apply workflows.
All integrations follow a common GitOps pattern:
- Detect which stacks and components changed using
atmos describe affected - Run
atmos terraform planfor each affected component/stack pair - Review plan output in the PR or CI/CD UI
- Apply changes on merge (or via manual trigger / label)
Change Detection with atmos describe affected
The atmos describe affected command is the foundation of all CI/CD integrations. It compares two Git
commits to produce a list of affected Atmos components and stacks.
More from cloudposse/atmos
atmos-design-patterns
Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration
15atmos-config
Project configuration: atmos.yaml structure, all sections, discovery, merging, base paths, settings, imports, profiles
12atmos-workflows
Workflow automation: multi-step workflows, Go template support, cross-component orchestration
12atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management
12atmos-stores
Store backends: AWS SSM, Azure Key Vault, Google Secret Manager, Redis, Artifactory configuration, hooks integration, cross-component data sharing
11atmos-stacks
Stack configuration: imports, inheritance, deep merging, locals, vars, settings, metadata, overrides
10