Atmos Manifests
Atmos Stack Manifests. Documentation: https://atmos.tools
| Type | object |
|---|---|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/atmos-manifests/latest.json |
| Source | https://atmos.tools/schemas/atmos/atmos-manifest/1.0/atmos-manifest.json |
Validate with Lintel
npx @lintel/lintel checkProperties
Import section
Terraform section
Helmfile section
Packer section
Vars section
Hooks section
Env section
Settings section
Local variables for use within templates. At file level (global, terraform, helmfile, packer sections), locals are file-scoped and do NOT inherit across file imports. At component level, locals inherit from base components via metadata.inherits (or the component field), similar to vars, with component-level locals taking precedence. Locals can reference each other within the same scope.
Components section
Overrides section
Workflows section
Dependencies section for declaring tool dependencies. Tools specified here will be automatically installed and made available when the component is provisioned.
Generate section for declarative file generation. Keys are filenames (must be quoted if containing dots), values are either string templates or objects that will be serialized based on file extension (.json, .yaml, .yml, .tf, .hcl).
One of
Definitions
Import section
Components section
Terraform section
Terraform components section
Terraform component manifest
Helmfile section
Helmfile components section
Helmfile component manifest
Packer section
Packer components section
packer component manifest
Command to execute
Component section
Metadata section
Settings section
Validation section
Validation manifest
Vars section
Env section
Local variables for use within templates. At file level (global, terraform, helmfile, packer sections), locals are file-scoped and do NOT inherit across file imports. At component level, locals inherit from base components via metadata.inherits (or the component field), similar to vars, with component-level locals taking precedence. Locals can reference each other within the same scope.
Backend type
Backend manifest
Remote state backend type
Backend manifest
Backend manifest
Overrides section
Depends_on section
Depends_on manifest
Spacelift section
Atlantis section
Workflows section
Workflow manifest
Providers section
Templates section
Hooks section
Generate section for declarative file generation. Keys are filenames (must be quoted if containing dots), values are either string templates or objects that will be serialized based on file extension (.json, .yaml, .yml, .tf, .hcl).
Provision section for component provisioning configuration
Workdir provisioner configuration for isolated component execution directories
Component source configuration for Just-in-Time (JIT) vendoring. Specifies where to fetch component code from. Supports go-getter compatible URIs.
Retry configuration for workflow steps
Retry configuration for source vendoring operations
Dependencies section for declaring tool dependencies. Tools specified here will be automatically installed and made available when the component is provisioned.
Tool dependencies with version specifications. Keys are tool names (e.g., 'terraform', 'kubectl', 'k9s') and values are version strings (e.g., '1.9.8', 'latest').
Component-level authentication configuration. Allows overriding or extending global auth providers and identities for specific components.
Authentication providers configuration. Keys are provider names, values are provider configurations.
Authentication provider configuration.
Authentication identities configuration. Keys are identity names, values are identity configurations.
Authentication identity configuration.
Specifies how an identity connects to a provider or chains from another identity.
Session configuration for authentication.
Web console access configuration.