#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

Hi, there. I surprised that it not covered from day 1 of hooks introduction
Can you please take a look?
github.com/cloudposse/atmos/issues/2799

Does anyone tried atmos.tools/changelog/tags-and-labels ?

For some reason, these doesn't work for me (I located them in most top _defaults.yaml):

  metadata:
    labels:
      some_tag: some_value
  vars:
    tags: !labels

Inside generated .tfvars.json after atmos terraform plan:

"tags": {
    "unrelated_tag": "foo"
  },

atmos v1.223.0

Running the curl install listed on the homepage of atmos, immediately ran into the following. Is this supposed to run as sudo? First time posting here, so let me know if this is the wrong way to go about reaching out.

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.4 LTS"

❓️ is there an atmos native way to arbitrarily look up things from a state backend, if they aren't technically managed by your stack?

Hey there 👋,

New to contributing, not totally sure this is the right place to raise this — point me elsewhere if so!

I finally had time to prototype the native RDS IAM auth idea I floated a while back in a discussion, I linked more context on the original issue but looking at adding atmos aws rds token, plus a rds onnect follow-on — both are draft PRs.

Would love a gut-check on whether it's worth pursuing and the right direction.

Wrote it all up here:
github.com/orgs/cloudposse/discussions/121#…

Anyone else experience fatal error: concurrent map iteration and map write when using DAG?

Hi, there. I am currently working with atmos helmfile and is there a way that the values from stack config gets applied automatically when running command atmos helmfile diff/apply <component> -s <stack>, instead of passing values filename manually like below in helmfile.yaml. Also atmos generated values file eg: aws-useast1-metrics-server.helmfile.vars.yaml are getting with stack identification values like namespace, environment, stg where some helm charts are failing with validation errors like chart doesn't allow those extra values. Thank you. @PePe Amengual

repositories:
  - name: metrics-server
    url: <https://kubernetes-sigs.github.io/metrics-server/>

releases:
  - name: metrics-server
    chart: metrics-server/metrics-server
    version: 3.13.0
    namespace: kube-system
    createNamespace: false
    force: false
    values:
      - aws-useast1-metrics-server.helmfile.vars.yaml

fyi github.com/cloudposse/atmos/issues/2839

Hi all 👋

Not entirely sure if this is the right channel or #atmos-dev, but I posted a proposal for dynamic file generation (for_each) in atmos scaffold, see: github.com/orgs/cloudposse/discussions/126. Would appreciate some feedback there 🙏.