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_PROFILEActivate configuration profiles (comma-separated). Equivalent to the
--profileflag.ATMOS_BASE_PATHBase path to
componentsandstacksfolders.- YAML Path:
base_path
- YAML Path:
ATMOS_VENDOR_BASE_PATHPath to vendor configuration file or directory containing vendor files.
- YAML Path:
vendor.base_path
- YAML Path:
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.- YAML Path:
components.terraform.init_run_reconfigure
- 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_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 Variables
ATMOS_GITHUB_TOKENBearer token for GitHub API requests, enabling authentication for private repositories.
ATMOS_GITHUB_USERNAMEGitHub username for OCI registry authentication to ghcr.io.
- YAML Path:
settings.github_username
- YAML Path:
ATMOS_BITBUCKET_TOKENApp password for Bitbucket API requests.
ATMOS_BITBUCKET_USERNAMEUsername for Bitbucket authentication.
ATMOS_GITLAB_TOKENPersonal Access Token (PAT) for GitLab authentication.
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
- Base Path — Configure base paths
- Logs — Configure logging
- Profiler — Configure performance profiling