versions.md
June 3, 2026 · View on GitHub
Version Compatibility: Atmos ↔ cloudposse/utils Provider
The cloudposse/utils Terraform provider embeds the Atmos Go library to perform
deep-merge operations on YAML and JSON.
Because deep-merge semantics can change between Atmos releases, the Atmos library version compiled into the
provider must match the Atmos CLI version you are running. A mismatch can cause the provider and Atmos to
produce different merge results for the same inputs, breaking deterministic infrastructure configuration.
Use the table below to pin both tools to compatible versions.
Note: The
2.xline is the actively developed release line. The1.xline receives parallel backport releases for users who cannot yet migrate. Where multiple provider releases share an Atmos version, only the latest release in each line is shown.
Version Compatibility: terraform-yaml-stack-config ↔ cloudposse/utils Provider
The cloudposse/terraform-yaml-stack-config module
uses the cloudposse/utils provider internally. Its modules/remote-state child module declares explicit provider
version constraints — if you source that child module in a root module, both the child's constraint and any
constraint declared by the root module must be satisfiable simultaneously.
Use the table below to pick a terraform-yaml-stack-config release that is compatible with your chosen
cloudposse/utils provider version.
terraform-yaml-stack-config | Required cloudposse/utils (root module) | Required cloudposse/utils (modules/remote-state) |
|---|---|---|
| v2.0.0 | >= 2.0.0, < 3.0.0 | >= 2.0.0, < 3.0.0 |
| v1.5.0–v1.8.0 | >= 1.7.1 | >= 1.7.1, < 2.0.0 |
| v1.1.1–v1.4.3 | >= 1.5.0 | = 1.5.0 |
| v1.0.0 | >= 1.2.0 | >= 1.2.0 |