atmos-schemas
Atmos JSON Schema System
Overview
Atmos uses JSON Schema (Draft 2020-12) to validate stack manifests, provide IDE auto-completion, and catch configuration errors early. The schema system has three layers:
-
Website manifest schema -- Published at
website/static/schemas/atmos/atmos-manifest/1.0/atmos-manifest.json, served athttps://atmos.tools/schemas/atmos/atmos-manifest/1.0/atmos-manifest.json, and registered with SchemaStore ashttps://json.schemastore.org/atmos-manifest.json. This is the public-facing schema for IDE integration. -
Embedded schemas -- Located under
pkg/datafetcher/schema/, compiled into the Atmos binary via Goembed. These are the schemas Atmos uses at runtime for validation. There are multiple embedded schemas:pkg/datafetcher/schema/atmos/manifest/1.0.json-- Minimal manifest schema (fallback).pkg/datafetcher/schema/stacks/stack-config/1.0.json-- Stack configuration validation schema. This is the primary schema used byatmos validate stacks.pkg/datafetcher/schema/config/global/1.0.json-- Global Atmos configuration schema.pkg/datafetcher/schema/vendor/package/1.0.json-- Vendor package manifest schema.
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