#atmos - July 2026

Hi, do you accept issues made by AI? I found a bug it seems and made codex to file the bug report here: github.com/cloudposse/atmos/issues/2680

Hello, I ran into an issue with Native CI in JIT vendored components, added a bug report for it: github.com/cloudposse/atmos/issues/2684
Basically if you source a component direct from github to use directly, and specify a workdir, the native ci planfile logic looks in the wrong spot for the planfile

Hi. Can you look into github.com/cloudposse/atmos/issues/2376 bug? It still exist in 1.222.0

so sick !

@Erik Osterman (Cloud Posse) Do you know if you can set authentication for an oci JIT source component? Or if it's documented somewhere specific? Specifically a terraform.$component.source.uri

Hey everyone! Wondering if anyone else has seen this behavior:

We noticed that after a recent update to cloudposse/github-action-setup-atmos@v3, our atmos terraform deploy and atmos terraform apply commands in GitHub Actions started completing instantly (0 seconds, exit code 0) with no terraform output — no init, no plan, no apply.

The install path changed from /home/runner/work/_actions/cloudposse/github-action-setup-atmos/atmos to /opt/hostedtoolcache/atmos-wrapper/1.222.0/x64. Actions runs using the old path on July 3 worked fine (5-minute deploys); runs using the new wrapper path on July 4+ silently no-op.

Workaround: Setting install-wrapper: "false" resolves it — deploy commands run terraform as expected.

Are we missing a configuration step for the wrapper, or is this a known issue with the latest release? Happy to provide workflow snippets or run logs if helpful. Thanks!

The recent changes to --help is very welcomed. It's a much better DX then providing all the help information.

Trying to implement a blue/green pattern in atmos. DAG doesn't work across multiple stacks yet does it?

really enjoying DAG, seems to be working decently with a PoC for targeted stack precedence