Installer atmos avec Homebrew, Nix, scoop

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• atmos

Historique du projet

The official README describes Atmos as a framework for orchestrating and operating infrastructure workflows across multiple cloud and DevOps toolchains. It emphasizes reusable components implemented as Terraform root modules, stack configurations in YAML, DRY configuration, vendoring, custom commands, GitOps capabilities, and policy controls.

The README also identifies Cloud Posse as a heavy internal user for automating cloud infrastructure with Terraform and Kubernetes, while saying the tool can automate any complex workflow. The generated README's copyright span covers 2017-2026, fitting Cloud Posse's long-running open-source infrastructure ecosystem.

Historique d'adoption

Atmos is distributed as a Homebrew formula and appears in Nix and Scoop in the input, which matches its cross-platform CLI positioning. The official website calls it free and open source and promotes installation, examples, CLI reference, and community support through Cloud Posse's SweetOps Slack and office hours.

The project has a fast-moving release line: official Git tags include early 0.x releases and later v1.x releases reaching v1.99.0. That matters to package maintainers because Atmos is both a CLI and an opinionated framework; changes in config discovery, stack behavior, and integrations can affect whole infrastructure repositories.

Modes d'utilisation

Atmos users define components, stacks, workflows, and custom commands, then run atmos commands locally or in CI/CD to describe, plan, apply, vendor, validate, and orchestrate infrastructure. The README highlights Terraform-native orchestration, backend and varfile generation, stack configuration, component libraries, vendoring, and workflow orchestration.

The CLI configuration docs define atmos.yaml as the main config file. Atmos searches the current directory, Git repository root, parent directories, the home directory, and system directories, and can merge multiple config files plus .atmos.d fragments. On Windows, docs recommend forward slashes in atmos.yaml paths.

Pourquoi les passionnés de paquets s'y intéressent

Atmos is package-nerd catnip because it is a CLI that encodes an entire infrastructure repo layout philosophy. Installing it is not just getting another terraform wrapper; it brings Cloud Posse's conventions for stacks, components, vendoring, custom commands, and GitOps into a portable binary.

Its config discovery order is especially important for packagers and shell users because the same atmos binary behaves differently depending on current directory, repo root, home config, and system config.

Chronologie

• 2017-2026: The generated official README carries Cloud Posse copyright across this span.
• 0.x: Official Git tags include early 0.0.2 and 0.1.0 releases.
• 1.x: Official Git tags show an active v1 release line reaching v1.99.0.
• Current: Official docs describe Terraform, OpenTofu, Helmfile, Ansible, Packer, and Devcontainers use cases.

Related projects

• Terraform and OpenTofu are primary IaC engines Atmos orchestrates.
• Helmfile, Ansible, Packer, Devcontainers, and Kubernetes are documented toolchain targets.
• Cloud Posse's Terraform modules, SweetOps community, and terraform-provider-utils are closely related ecosystem pieces.

Sources

• https://atmos.tools/
• https://atmos.tools/cli/configuration/
• https://github.com/cloudposse/atmos#readme