@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2151

@RB thanks for the PRs. As soon as you're ready, nudge us in here.

@RB https://github.com/cloudposse/atmos/pull/2158

Did you personally validate this is working?

Please review some gha fixes in the atmos repo

https://github.com/cloudposse/atmos/pull/2160/changes

@Billy Atkins shared that atmos is now live in the Google Code Wiki https://codewiki.google/github.com/cloudposse/atmos

I would like to contribute concurrent component provisioning, here is a proposal for discussion:
https://github.com/cloudposse/atmos/pull/2159

Currently we are using our own github actions workflows that are patched to implement dependencies, but it is really ugly to do it via GH and matrix,

Possibly it should be implemented after this one: https://github.com/cloudposse/atmos/pull/1891

@Andriy Knysh (Cloud Posse) this was confirmed by @MB https://sweetops.slack.com/archives/C031919U8A0/p1772642542133729?thread_ts=1772637524.256159&channel=C031919U8A0&message_ts=1772642542.133729

Just testing out some of the new Atmos agent skills and ran into this install issue. Am I doing something wrong?

❯ /plugin marketplace add cloudposse/atmos
  ⎿  Error: Invalid schema:
     /Users/rosesecurity/.claude/plugins/marketplaces/cloudposse-atmos/.claude-plugin/marketplace.json
     plugins.0.source: Invalid input

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2130

@Andriy Knysh (Cloud Posse) docs only https://github.com/cloudposse/atmos/pull/2132

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2127

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2093

Little Ansible integration promotion if the team supports this: https://github.com/cloudposse/atmos/pull/2116

https://github.com/cloudposse/atmos/pull/2109

Followup fixes to GCP WIF auth on GITHUB, tested this time properly on our CI.

@Andriy Knysh (Cloud Posse) @Erik Osterman (Cloud Posse)

@Michael tests are failing https://github.com/cloudposse/atmos/pull/2108

@Andriy Knysh (Cloud Posse) this is ready for merge and was validated by @Zack https://github.com/cloudposse/atmos/pull/2111

@Andriy Knysh (Cloud Posse) this was validated by @Jonathan Rose
https://github.com/cloudposse/atmos/pull/2107

@Andriy Knysh (Cloud Posse) a minor one https://github.com/cloudposse/atmos/pull/2103

@Andriy Knysh (Cloud Posse) I think we can merge this when you get a chance https://github.com/cloudposse/atmos/pull/2042

Cc @Michael

@Stephen has joined the channel

@Kyle Decot has joined the channel

@Andriy Knysh (Cloud Posse) roadmap clean up https://github.com/cloudposse/atmos/pull/2062

@Michael regarding ansible support, to what extent have you had the opportunity to dog food it?

Did v1.205.1 publish the release? We haven't been able to download from Cloudsmith yet

https://github.com/cloudposse/atmos/pull/2051 cc @Andriy Knysh (Cloud Posse) @Erik Osterman (Cloud Posse)

google cloud auth provider implementation following AWS/Azure with gcp-adc/gcp-wif, service account impersonation, etc

We encountered an issue after attempting to mgirate from apt-installed tools in Geodesic to Atmos Toolchain. Looking for insight into whether the toolchain introduces any environment variables that could affect workspace or backend configuration.

We source the toolchain on Geodesic startup:

if command -v atmos &>/dev/null; then
    eval "$(atmos toolchain env --chdir / 2>/dev/null)" || true
fi

With this atmos.yaml configuration addition:

toolchain:
  file_path: ".tool-versions"
  tools_dir: ".tools"

Local builds and Terraform operations work correctly but Spacelift workers fail across the board with this error:

│ Error: Backend configuration changed
│ 
│ A change in the backend configuration has been detected, which may require
│ migrating existing state.
│ 
│ If you wish to attempt automatic migration of the state, use "tofu init
│ -migrate-state".
│ If you wish to store the current configuration with no changes to the
│ state, use "tofu init -reconfigure".

Does Atmos Toolchain set any environment variables (e.g., TF_* or workspace-related) that could cause Terraform/OpenTofu to detect a backend change? I know this is a super broad question with lots of variables but curious if you had any recommendations

@Andriy Knysh (Cloud Posse) doc correction https://github.com/cloudposse/atmos/pull/2045

@Andriy Knysh (Cloud Posse) simple refactoring moving toolchain into pkg/ where it belongs. no logic change.
https://github.com/cloudposse/atmos/pull/2041

Reviving this for collaboration if anyone is interested in a new Atmos Ansible component type!

https://github.com/cloudposse/atmos/pull/2042

@Zack would you be open to helping us validate https://github.com/cloudposse/atmos/pull/2039

@Andriy Knysh (Cloud Posse) this is ready https://github.com/cloudposse/atmos/pull/2038

Just checking in if the v1.205.0 package was pushed to Cloudsmith. Didn't see the update in packages so I was curious if that is still the pattern or if it will be installed a different way

@Andriy Knysh (Cloud Posse) this fixes more redirects https://github.com/cloudposse/atmos/pull/2021

This PR adds some spinners to improve the user experience for various validation commands. Feel free to approve or disregard: https://github.com/cloudposse/atmos/pull/1951

@Andriy Knysh (Cloud Posse) another small fix for the sidebar menu so it auto scrolls to the open section. https://github.com/cloudposse/atmos/pull/2009

@Andriy Knysh (Cloud Posse) this is ready for review https://github.com/cloudposse/atmos/pull/1979

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/1981 (small one)

@Andriy Knysh (Cloud Posse) a minor one cleaning up bullet points https://github.com/cloudposse/atmos/pull/1999

@Andriy Knysh (Cloud Posse) another simple one https://github.com/cloudposse/atmos/pull/1988

@Andriy Knysh (Cloud Posse) simple one https://github.com/cloudposse/atmos/pull/1986

ah yes, that changed to your second version. I'll fix desc! thanks for reporting.

Random observation but I may be doing this wrong. The help menu for atmos toolchain shows:

     $ atmos toolchain add <tool-name> <version>

But that fails and the commands that work are:

atmos toolchain add opentofu/opentofu@1.7.10

Am I doing this correctly? If so, I can open a PR to update the help menu

@Andriy Knysh (Cloud Posse) small one https://github.com/cloudposse/atmos/pull/1975

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/1969 (website only change)

@Andriy Knysh (Cloud Posse) now that we cut, 1.204.0, would like to clear these PRs out

@Andriy Knysh (Cloud Posse) documentation clean up https://github.com/cloudposse/atmos/pull/1952

@Andriy Knysh (Cloud Posse) are you able to test/validate https://github.com/cloudposse/atmos/pull/1934