Atmos Project Configuration FAQs

Question 1

What is the primary purpose of the atmos-config skill?

Accepted Answer

It serves as the central configuration authority for Atmos projects, defining how stacks, components, and workflows are discovered and executed by the CLI.

Question 2

Can I override atmos.yaml settings using environment variables?

Accepted Answer

Yes, almost every setting in atmos.yaml can be overridden via environment variables using the ATMOS_ prefix, such as ATMOS_BASE_PATH.

Question 3

How does Atmos handle multiple configuration files?

Accepted Answer

Atmos uses a deep-merging strategy where files found in various locations (CLI flags, current directory, repo root, etc.) are combined, with earlier sources taking precedence.

Question 4

What is configuration discovery order in Atmos?

Accepted Answer

Atmos searches for configuration in a specific sequence: CLI flags, environment variables, active profiles, the local directory, the Git root, and finally user or system-level directories.

Question 5

Does this skill support modular configuration organization?

Accepted Answer

Absolutely. It supports the 'import' section, which allows you to split large configurations into smaller, manageable files like auth.yaml or stores.yaml and merge them into the main config.

Atmos Project Configuration

Key Features

Use Cases

Atmos Project Configuration

Key Features

Use Cases