atmos-validation
Atmos Validation Framework
Overview
Atmos provides a built-in validation framework that enforces policies and schema constraints on stack configurations before infrastructure is provisioned. Validation ensures clean, correct, and compliant configurations across teams and environments. Atmos supports three types of native validation:
- JSON Schema -- Validates the structure and types of component configurations
- Open Policy Agent (OPA) -- Enforces custom business rules using Rego policies
- EditorConfig Checker -- Ensures consistent coding styles across files
Validation runs automatically before atmos terraform plan and atmos terraform apply, preventing
misconfigured infrastructure from being provisioned. It can also run on-demand using the
atmos validate component and atmos validate stacks commands.
Validation Commands
atmos validate component
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