Environment Variables
Most YAML settings in atmos.yaml can also be defined by environment variables. This is helpful for local development, CI/CD pipelines, and environment-specific overrides.
Configuration Variables
These environment variables configure Atmos behavior and can override settings in atmos.yaml.
ATMOS_CLI_CONFIG_PATHWhere to find
atmos.yaml. Path to a folder whereatmos.yamlCLI config file is located (e.g./config).ATMOS_CONFIGPaths to specific configuration files (comma-separated). Equivalent to
--config.ATMOS_CONFIG_PATHPaths to search for Atmos configuration (comma-separated). Equivalent to
--config-path.ATMOS_PROFILEActivate configuration profiles (comma-separated). Equivalent to the
--profileflag.ATMOS_BASE_PATHBase path to
componentsandstacksfolders.- YAML Path:
base_path
- YAML Path:
ATMOS_CHDIRChange the working directory before executing any command. Equivalent to
--chdir.ATMOS_VENDOR_BASE_PATHPath to vendor configuration file or directory containing vendor files.
- YAML Path:
vendor.base_path
- YAML Path:
Version Management
ATMOS_USE_VERSIONSpecify which version of Atmos to use. If the running version doesn't match, Atmos automatically downloads and re-executes with the requested version. Equivalent to
--use-version.- Example:
ATMOS_USE_VERSION=1.160.0 atmos terraform plan
- Example:
ATMOS_VERSIONConvenience alias for
ATMOS_USE_VERSION.ATMOS_VERSION_ENFORCEMENTVersion constraint enforcement mode. Controls behavior when version constraints are defined in
atmos.yaml.
Terminal and Output Variables
ATMOS_NO_COLORDisable colored output. Equivalent to
--no-color.NO_COLORStandard convention to disable colored output. Recognized alongside
ATMOS_NO_COLOR.ATMOS_FORCE_COLORForce TrueColor output even when terminal detection says otherwise. Equivalent to
--force-color.ATMOS_FORCE_TTYForce TTY mode for terminal output. Equivalent to
--force-tty.COLUMNSStandard convention supplying the terminal width when output is not a TTY (pipes, recordings, CI). Atmos lays out width-sensitive output (such as help screens) at this width. Ignored when a real terminal size is available; capped by
settings.terminal.max_widthwhen configured.ATMOS_REDIRECT_STDERRRedirect stderr to a file. Equivalent to
--redirect-stderr.
Component Variables
ATMOS_COMPONENTS_TERRAFORM_COMMANDThe executable to be called by
atmoswhen running Terraform commands.- YAML Path:
components.terraform.command
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_BASE_PATHBase path to Terraform components.
- YAML Path:
components.terraform.base_path
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_APPLY_AUTO_APPROVEIf set to
true, auto-approve Terraform apply.- YAML Path:
components.terraform.apply_auto_approve
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_DEPLOY_RUN_INITRun
terraform initwhen executingatmos terraform deploycommand.- YAML Path:
components.terraform.deploy_run_init
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_INIT_RUN_RECONFIGURERun
terraform init -reconfigurewhen executingatmos terraformcommands. Deprecated in favor ofATMOS_COMPONENTS_TERRAFORM_INIT_RECONFIGURE.- YAML Path:
components.terraform.init_run_reconfigure
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_INIT_MODEControls when Atmos runs
terraform initautomatically:auto(default, skip when nothing relevant changed),always, ornever.- YAML Path:
components.terraform.init.mode
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_INIT_RECONFIGUREControls when Atmos adds
-reconfigureto an automaticterraform init:auto(default, only when the backend changed),always, ornever.- YAML Path:
components.terraform.init.reconfigure
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_INIT_UPGRADEControls when Atmos adds
-upgradeto an automaticterraform init:never(default),auto(only when Terraform/OpenTofu reports it's required), oralways.- YAML Path:
components.terraform.init.upgrade
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_INIT_PASS_VARSPass the generated varfile to
terraform initusing the--var-fileflag.- YAML Path:
components.terraform.init.pass_vars
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_PLAN_SKIP_PLANFILESkip writing the plan to a file by not passing the
-outflag.- YAML Path:
components.terraform.plan.skip_planfile
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_AUTO_GENERATE_BACKEND_FILEIf set to
true, auto-generate Terraform backend config files.- YAML Path:
components.terraform.auto_generate_backend_file
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_PLUGIN_CACHEIf set to
true, enable Terraform provider plugin caching.- YAML Path:
components.terraform.plugin_cache
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_PLUGIN_CACHE_DIRCustom directory for Terraform provider plugin cache. If not set, uses the XDG cache directory.
- YAML Path:
components.terraform.plugin_cache_dir
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_CACHE_ENABLEDIf set to
true, enable the Terraform registry cache proxy for provider and module registry traffic.- YAML Path:
components.terraform.cache.enabled - Default:
false
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_CACHE_LOCATIONCustom root directory for the Terraform registry cache. Pin this to a stable path in CI when the cache should be reused across
atmosinvocations.- YAML Path:
components.terraform.cache.location
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_AUTO_PROVISION_WORKDIR_FOR_OUTPUTSIf set to
false, disable automatic JIT workdir provisioning beforeterraform initduring!terraform.output/atmos.Componentevaluation.- YAML Path:
components.terraform.auto_provision_workdir_for_outputs - Default:
true
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_FLAGS_LOCK_TIMEOUTDefault value for terraform's
-lock-timeoutflag (e.g.5m). Overrides theatmos.yamlvalue; overridden by stack-level, component-level, and CLI-typed flags. See Flags.- YAML Path:
components.terraform.flags.lock_timeout
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_FLAGS_LOCKDefault value for terraform's
-lockflag.- YAML Path:
components.terraform.flags.lock
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_FLAGS_PARALLELISMDefault value for terraform's
-parallelismflag.- YAML Path:
components.terraform.flags.parallelism
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_FLAGS_REFRESHDefault value for terraform's
-refreshflag.- YAML Path:
components.terraform.flags.refresh
- YAML Path:
ATMOS_COMPONENTS_TERRAFORM_FLAGS_COMPACT_WARNINGSDefault value for terraform's
-compact-warningsflag.- YAML Path:
components.terraform.flags.compact_warnings - Default:
false
- YAML Path:
ATMOS_COMPONENTS_HELMFILE_COMMANDThe executable to be called by
atmoswhen running Helmfile commands.- YAML Path:
components.helmfile.command
- YAML Path:
ATMOS_COMPONENTS_HELMFILE_BASE_PATHPath to helmfile components.
- YAML Path:
components.helmfile.base_path
- YAML Path:
ATMOS_COMPONENTS_HELMFILE_USE_EKSIf set to
true, downloadkubeconfigfrom EKS before executingatmos helmfilecommands.- YAML Path:
components.helmfile.use_eks
- YAML Path:
ATMOS_COMPONENTS_HELMFILE_KUBECONFIG_PATHPath to write the
kubeconfigfile.- YAML Path:
components.helmfile.kubeconfig_path
- YAML Path:
ATMOS_COMPONENTS_HELMFILE_HELM_AWS_PROFILE_PATTERNPattern for AWS profile to use when executing
atmos helmfilecommands.- YAML Path:
components.helmfile.helm_aws_profile_pattern
- YAML Path:
ATMOS_COMPONENTS_HELMFILE_CLUSTER_NAME_PATTERNPattern for EKS cluster name to use when executing
atmos helmfilecommands.- YAML Path:
components.helmfile.cluster_name_pattern
- YAML Path:
Stack Variables
ATMOS_STACKS_BASE_PATHBase path to Atmos stack manifests.
- YAML Path:
stacks.base_path
- YAML Path:
ATMOS_STACKS_INCLUDED_PATHSList of paths to use as top-level stack manifests.
- YAML Path:
stacks.included_paths
- YAML Path:
ATMOS_STACKS_EXCLUDED_PATHSList of paths to not consider as top-level stacks.
- YAML Path:
stacks.excluded_paths
- YAML Path:
ATMOS_STACKS_NAME_PATTERNStack name pattern to use as Atmos stack names.
- YAML Path:
stacks.name_pattern
- YAML Path:
ATMOS_STACKS_NAME_TEMPLATEStack name Golang template to use as Atmos stack names.
- YAML Path:
stacks.name_template
- YAML Path:
Workflow and Schema Variables
ATMOS_WORKFLOWS_BASE_PATHBase path to Atmos workflows.
- YAML Path:
workflows.base_path
- YAML Path:
ATMOS_SCHEMAS_JSONSCHEMA_BASE_PATHBase path to JSON schemas for component validation.
- YAML Path:
schemas.jsonschema.base_path
- YAML Path:
ATMOS_SCHEMAS_OPA_BASE_PATHBase path to OPA policies for component validation.
- YAML Path:
schemas.opa.base_path
- YAML Path:
ATMOS_SCHEMAS_ATMOS_MANIFESTPath to JSON Schema to validate Atmos stack manifests.
- YAML Path:
schemas.atmos.manifest
- YAML Path:
Logging and Profiling Variables
ATMOS_LOGS_FILEThe file to write Atmos logs to (
/dev/stdout,/dev/stderr,/dev/null, or a file path).- YAML Path:
logs.file
- YAML Path:
ATMOS_LOGS_LEVELLogs level:
Trace,Debug,Info,Warning,Off.- YAML Path:
logs.level
- YAML Path:
ATMOS_PROFILER_ENABLEDEnable or disable the pprof HTTP profiling server.
- YAML Path:
profiler.enabled
- YAML Path:
ATMOS_PROFILER_HOSTHost address for the profiling server.
- YAML Path:
profiler.host
- YAML Path:
ATMOS_PROFILER_PORTPort for the profiling server.
- YAML Path:
profiler.port
- YAML Path:
ATMOS_PROFILE_FILEWrite profiling data to the specified file.
- YAML Path:
profiler.file
- YAML Path:
ATMOS_PROFILE_TYPEType of profile to collect:
cpu,heap,allocs,goroutine,block,mutex,threadcreate,trace.- YAML Path:
profiler.profile_type
- YAML Path:
Settings Variables
ATMOS_SETTINGS_LIST_MERGE_STRATEGYSpecifies how lists are merged:
replace,append,merge.- YAML Path:
settings.list_merge_strategy
- YAML Path:
ATMOS_VERSION_CHECK_ENABLEDEnable/disable Atmos version checks for updates.
- YAML Path:
version.check.enabled
- YAML Path:
Authentication and Token Injection
GITHUB_TOKEN/ATMOS_GITHUB_TOKENGitHub token for private module downloads and API access.
ATMOS_GITHUB_TOKENtakes precedence overGITHUB_TOKEN. Automatically injected into Terraform environments whenATMOS_INJECT_GITHUB_TOKEN=true(default).ATMOS_PRO_GITHUB_TOKENGitHub token for private module downloads and Atmos-native git operations (vendoring,
source:provisioning, go-getter), preferred ahead ofATMOS_GITHUB_TOKENandGITHUB_TOKEN. Typically a token brokered by Atmos Pro.ATMOS_INJECT_GITHUB_TOKENInject the GitHub token into component environments. Default:
true. Set tofalseto prevent token injection.ATMOS_GITHUB_CLIName (or path) of the GitHub CLI used to obtain a token when no
GITHUB_TOKEN/ATMOS_GITHUB_TOKENis set. Defaults togh. Atmos runs<cli> auth tokenonly as a last resort, after the flag and environment variables. Set it to an empty value to disable the CLI fallback entirely, or to a nonexistent binary to force anonymous (unauthenticated) GitHub access — useful for testing the public artifact/download paths (subject to GitHub's 60 requests/hour unauthenticated rate limit).GITHUB_USERNAME/GITHUB_ACTOR/ATMOS_GITHUB_USERNAMEGitHub username for OCI registry authentication to ghcr.io.
GITHUB_ACTORis automatically set in GitHub Actions.- YAML Path:
settings.github_username
- YAML Path:
GITLAB_TOKEN/ATMOS_GITLAB_TOKENGitLab token for private module downloads.
ATMOS_INJECT_GITLAB_TOKENInject the GitLab token into component environments.
BITBUCKET_TOKEN/ATMOS_BITBUCKET_TOKENApp password for Bitbucket API requests and private module downloads.
ATMOS_INJECT_BITBUCKET_TOKENInject the Bitbucket token into component environments.
BITBUCKET_USERNAMEUsername for Bitbucket authentication. Bitbucket requires a valid username and does not accept dummy values like
x-access-token.
GitHub Enterprise Server (GHES)
These variables point Atmos at a GitHub Enterprise Server instance instead of public
github.com. GITHUB_SERVER_URL and GITHUB_API_URL are the same variables GitHub Actions
already exports on both github.com and GHES runners, so CI configuration typically needs no
changes.
The toolchain (aqua-registry tools and their release assets) is a separate concern from
where your own repositories live: aqua-registry tools are hosted on public github.com even
when your repositories are on GHES, so the toolchain does not follow GITHUB_SERVER_URL /
GITHUB_API_URL. Use the ATMOS_TOOLCHAIN_* variables instead — for example, to point the
toolchain at a corporate release proxy or mirror.
GITHUB_SERVER_URLBase URL of the GitHub (or GHES) web/clone host for your own repositories. Default:
https://github.com. Used by the CI provider, imports/vendoring raw fetches, thepkg/githubAPI client (releases, tags, artifacts), the token host allowlist, and token injection host recognition.GITHUB_SERVER_URL=https://github.example.comGITHUB_API_URLBase URL of the GitHub (or GHES) REST API for your own repositories. Default:
https://api.github.com; on GHES this is typicallyhttps://<host>/api/v3.GITHUB_API_URL=https://github.example.com/api/v3ATMOS_TOOLCHAIN_GITHUB_URLBase URL used for toolchain release assets and source archives (
github_releaseandgithub_archivetool types). Default:https://github.com. Independent ofGITHUB_SERVER_URL.ATMOS_TOOLCHAIN_GITHUB_API_URLBase URL used for toolchain repository API calls (e.g. fetching a tool's available versions). Default:
https://api.github.com. Independent ofGITHUB_API_URL.ATMOS_TOOLCHAIN_AQUA_REGISTRY_URLBase URL of the aqua-registry raw content mirror (serves
registry.yamland per-packagepkgs/<name>/registry.yamlfiles). Default:https://raw.githubusercontent.com/aquaproj/aqua-registry/main.ATMOS_TOOLCHAIN_AQUA_REGISTRY_URL=https://releases.corp.example.com/aqua-registry/main
The bare owner/repo and literal github.com/owner/repo shorthand forms (imports, vendoring,
atmos git clone, AI skill sources, etc.) always resolve to public github.com — a bare
hostname can't be distinguished from a relative path, so shorthand detection can't safely guess
a GHES host from either form. On GHES, write the full URL instead (e.g.
https://github.example.com/owner/repo), with one exception: AI skill sources also accept the
actual configured GHES host without a scheme (github.example.com/owner/repo), since a skill
source is always a repository reference, never a local path. Imports and vendor manifests need
the explicit scheme even for the real GHES host. atmos git clone has no shorthand form at all
(on github.com or GHES); it always needs a full URI (HTTPS, SCP-style, or go-getter syntax).
Your GitHub token (ATMOS_GITHUB_TOKEN, GITHUB_TOKEN, --github-token, or gh auth token) is
only ever sent to an endpoint under two conditions:
- The request's actual destination is
https.GITHUB_SERVER_URL/GITHUB_API_URLand theATMOS_TOOLCHAIN_*variables above may resolve to a plainhttp://endpoint (this is only expected in local testing); Atmos never attaches the token to a request against a non-httpsdestination, since doing so would send it over the network in cleartext. This is re-checked against the request that is actually about to go out on the wire, not just the URL you configured: an HTTPS endpoint that redirects down to plainhttp://on the same host never receives the token on that redirected request either. - The request's actual destination belongs to an approved host. For your own repositories
(the CI provider, imports/vendoring, the
pkg/githubAPI client, and the artifact/cache backends), the approved hosts areGITHUB_SERVER_URL's server, API, and upload hosts. Your token is resolved without regard to host, so it is also treated as scoped toGITHUB_SERVER_URL's host for the toolchain installer and the aqua-registry client: it is forwarded toATMOS_TOOLCHAIN_GITHUB_URL/ATMOS_TOOLCHAIN_GITHUB_API_URLonly when both resolve to that same host asGITHUB_SERVER_URL/GITHUB_API_URL. By default the toolchain endpoints point at publicgithub.com, so on a GHES instance the toolchain fetches proceed unauthenticated unless you explicitly pointATMOS_TOOLCHAIN_GITHUB_URL/ATMOS_TOOLCHAIN_GITHUB_API_URLat your own GHES host too. This host check, like thehttpscheck above, is re-evaluated against every request Atmos actually sends -- including every hop of an automatic redirect -- so a redirect to an unapproved host (e.g. GitHub's own pre-signed, unauthenticated blob-storage redirect for an artifact download) never carries the token along, even when that redirect target is itselfhttps.
Both rules apply independently everywhere Atmos builds an authenticated GitHub request or
client (the CI provider, imports/vendoring, the pkg/github API client, the artifact/cache
backends, the toolchain installer, and the aqua-registry client).
AI Integration
ATMOS_AIEnable AI-powered analysis of command output. When
true, command output is sent to the configured AI provider for analysis. Equivalent to the--aiflag. Requires AI configuration inatmos.yaml.- Example:
ATMOS_AI=true atmos terraform plan vpc -s prod
- Example:
ATMOS_SKILLSpecify one or more AI skills for domain-specific analysis context (comma-separated). Equivalent to the
--skillflag. RequiresATMOS_AI=trueor--aiflag. Each skill's system prompt is prepended to the AI analysis for deeper, domain-aware insights.- Example:
ATMOS_AI=true ATMOS_SKILL=atmos-terraform,atmos-stacks atmos terraform plan vpc -s prod
- Example:
ANTHROPIC_API_KEY/ATMOS_ANTHROPIC_API_KEYAPI key for the Anthropic Claude AI provider.
OPENAI_API_KEY/ATMOS_OPENAI_API_KEYAPI key for the OpenAI GPT AI provider.
GEMINI_API_KEY/ATMOS_GEMINI_API_KEYAPI key for the Google Gemini AI provider.
XAI_API_KEY/ATMOS_XAI_API_KEYAPI key for the xAI Grok AI provider.
ATMOS_AI_SEND_CONTEXTControl whether stack configurations are sent to the AI provider for context-aware answers. Default:
false.ATMOS_AI_MCPSpecify which MCP servers to use (comma-separated). Skips automatic server routing and starts only the specified servers. Equivalent to the
--mcpflag onatmos ai ask,atmos ai chat, andatmos ai exec.- Example:
ATMOS_AI_MCP=aws-iam,aws-billing atmos ai ask "List admin roles and their costs"
- Example:
ATMOS_AI_INCLUDEAdd glob patterns to include in AI context (comma-separated). Equivalent to the
--includeflag.- Example:
ATMOS_AI_INCLUDE="stacks/**/*.yaml" atmos ai ask "Describe our stacks"
- Example:
ATMOS_AI_EXCLUDEAdd glob patterns to exclude from AI context (comma-separated). Equivalent to the
--excludeflag.- Example:
ATMOS_AI_EXCLUDE="**/secrets/**" atmos ai ask "Analyze our config"
- Example:
ATMOS_AI_NO_AUTO_CONTEXTDisable automatic context discovery. Equivalent to the
--no-auto-contextflag. Default:false.ATMOS_AI_NO_TOOLSDisable tool execution for faster, simpler queries. Equivalent to the
--no-toolsflag. Default:false.ATMOS_AI_FORMATOutput format for
atmos ai exec:text,json, ormarkdown. Equivalent to the--formatflag. Default:text.ATMOS_AI_OUTPUTOutput file path for
atmos ai exec. Equivalent to the--outputflag. Default: stdout.ATMOS_AI_CONTEXTInclude stack context in the prompt for
atmos ai exec. Equivalent to the--contextflag. Default:false.ATMOS_AI_PROVIDEROverride AI provider for
atmos ai exec(e.g.,anthropic,openai,gemini). Equivalent to the--providerflag.ATMOS_AI_SESSIONSession ID for conversation context in
atmos ai execandatmos ai chat. Equivalent to the--sessionflag.
Processing Flags
ATMOS_PROCESS_TEMPLATESEnable/disable Go template processing in Atmos manifests.
ATMOS_PROCESS_FUNCTIONSEnable/disable YAML function processing in Atmos manifests.
ATMOS_SKIPSkip processing specific Atmos YAML functions (comma-separated).
Terraform Integration
ATMOS_SKIP_INITSkip
terraform initbefore running commands.ATMOS_INIT_PASS_VARSPass the generated varfile to
terraform init.ATMOS_APPEND_USER_AGENTCustomize the User-Agent string sent with Terraform requests.
ATMOS_AUTO_GENERATE_BACKEND_FILEOverride the
auto_generate_backend_filesetting fromatmos.yaml.ATMOS_INIT_RUN_RECONFIGUREOverride the
init_run_reconfiguresetting fromatmos.yaml. Deprecated in favor ofATMOS_INIT_RECONFIGURE.ATMOS_INIT_MODEOverride the
--init-modeflag /components.terraform.init.modesetting:auto(default),always, ornever.ATMOS_INIT_RECONFIGUREOverride the
--init-reconfigureflag /components.terraform.init.reconfiguresetting:auto(default),always, ornever.ATMOS_INIT_UPGRADEOverride the
--init-upgradeflag /components.terraform.init.upgradesetting:auto(default),always, ornever.ATMOS_TERRAFORM_VERIFY_PLANSet to
trueto force planfile drift verification (fail on drift) onatmos terraform deploy, equivalent to--verify-plan. Set tofalseto disable verification (equivalent to--verify-plan=false), overriding config and the CI default. See Planfile drift verification.
Atmos Pro
ATMOS_PRO_BASE_URLAtmos Pro API base URL.
ATMOS_PRO_ENDPOINTAtmos Pro API endpoint.
ATMOS_PRO_WORKSPACE_IDAtmos Pro workspace identifier. Not a secret.
ATMOS_PRO_TOKENBearer token obtained via OIDC token exchange (advanced). See Pro authentication.
ATMOS_UPLOAD_STATUSUpload plan status to Atmos Pro after Terraform commands.
Telemetry
ATMOS_TELEMETRY_ENABLEDEnable anonymous telemetry reporting. Default:
true.ATMOS_TELEMETRY_TOKENTelemetry authentication token.
ATMOS_TELEMETRY_ENDPOINTCustom telemetry endpoint URL.
Experimental Features
ATMOS_EXPERIMENTALControl experimental command behavior. Options:
silence,disable,warn(default),error.
Toolchain
ATMOS_TOOL_VERSIONSPath to a tool-versions file for version pinning.
ATMOS_TOOLCHAIN_PATHDirectory where Atmos installs managed tools.
XDG Base Directories
ATMOS_XDG_CACHE_HOME/XDG_CACHE_HOMEOverride the cache directory. Default:
~/.cache.ATMOS_XDG_DATA_HOME/XDG_DATA_HOMEOverride the data directory. Default:
~/.local/share.ATMOS_XDG_CONFIG_HOME/XDG_CONFIG_HOMEOverride the config directory. Default:
~/.config.
Git Operations
ATMOS_REPO_PATHPath to the cloned target repository for
describe affected.ATMOS_REFGit reference for comparison in
describe affected.ATMOS_SHAGit commit SHA for comparison in
describe affected.ATMOS_SSH_KEYPath to SSH private key for Git operations.
ATMOS_SSH_KEY_PASSWORDSSH key encryption password.
ATMOS_CLONE_TARGET_REFClone target Git reference for comparison operations.
ATMOS_INCLUDE_DEPENDENTSInclude dependent components in
describe affectedoutput.
Context Variables
Some commands spawn interactive shells with environment variables set to provide context. These are set by Atmos, not by users:
ATMOS_COMPONENT- The name of the active component.
ATMOS_SHELL_WORKING_DIR- The directory from which native commands should be run.
ATMOS_SHLVL- The depth of Atmos shell nesting. When present, indicates shell was spawned by Atmos.
ATMOS_STACK- The name of the active stack.
ATMOS_TERRAFORM_WORKSPACE- The name of the Terraform workspace in which Terraform commands should be run.
PS1- When a custom shell prompt has been configured, the prompt is set via
PS1. TF_CLI_ARGS_*- Terraform CLI arguments to be passed to Terraform commands.
See Also
- CLI Configuration — Overview of CLI configuration
- Global Flags — Flag reference with environment variable equivalents
- Environment Variable Injection — Configure the
env:section inatmos.yamlto inject variables into tools - Stack Environment Variables — Component-level environment variables
- AI Configuration — AI provider setup and configuration
- Profiles — Environment-specific configuration overrides
- Logs — Configure logging
- Profiler — Configure performance profiling