#atmos-dev - March 2026

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

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

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

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

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) this was confirmed by @MB https://sweetops.slack.com/archives/C031919U8A0/p1772642542133729?thread_ts=1772637524.256159&channel=C031919U8A0&message_ts=1772642542.133729

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

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

Please review some gha fixes in the atmos repo

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

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

Did you personally validate this is working?

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

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

I loosed the requirements on issue templates, and added an AI prompt template for feature requests.

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

@RB may need your help to finish this https://github.com/cloudposse/atmos/pull/2174#issuecomment-4052196897

@Andriy Knysh (Cloud Posse) this was hand validated by me (against examples/toolchain) and resolves a few of the recurring problems we've been having.
• Package dependency is not accessible after install.
• Uninstall command not removing package dependencies.
After this change, finally one-shotting, toolchain installation should be possible or working with atmos terraform commands.

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

@Andriy Knysh (Cloud Posse) I ran into this defining some custom commands. Manually verified this works for me.

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

Thoughts on an import_if param ?

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

What do you guys think of having atmos plugins so each subcommand (validate/describe/terraform/helmfile) can be its own separate repo with its own versioned binary?

This way atmos can be a "shell" of a program and can be extendable e.g. you can do something like this

atmos plugin add validate@1.0.0
atmos plugin add terraform@1.2.3
atmos plugin add opentofu@2.0.0
etc

I recall we talked about a switch that would explain where every key came from post deep merge. This should give us that via --explain

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

Thoughts on linting stack yaml ?

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

A possible way to improve the stack deep merge by 3.5 times

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

Last one, thoughts on adding a description key for humans and for ai context

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

@RB please start with PRDs for all the features. see docs/prds; without the PRD, cannot assess the scope easily and implementations tend to not follow conventions.

This PR fixes the last HIGH severity security issue in atmos

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

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

reduce ExecuteDescribeStacks cyclomatic complexity 247→10 + near-100% unit test coverage

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

Can we include the openssf scorecard in the atmos repo to improve security score ?

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

prd to track and decrease cyclomatic complexity in order to improve test coverage and thus reduce future bugs

Related PRs

• https://github.com/cloudposse/atmos/pull/2226
• https://github.com/cloudposse/atmos/pull/2225
• https://github.com/cloudposse/atmos/pull/2204

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2229
This fixes the problem where users try to log into the console with multiple identities and get an error from AWS.

Improve test coverage, please review

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

do we have any tests that check for “speed” so an SLA/SLO can be created for various atmosy things?

@Andriy Knysh (Cloud Posse) this was validated by @Alexander Matveev
https://github.com/cloudposse/atmos/pull/2143

cc @Sean

@Charles Smith I looked into what you reported on Office Hours.
https://github.com/cloudposse/atmos/pull/2254

@Andriy Knysh (Cloud Posse): @Zack confirmed this fix is working: https://github.com/cloudposse/atmos/pull/2253

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2264 just improved the error messaging from Atmos uploads.

Could i get a review to close this small security finding from github codeql?

fix: clear-text logging of sensitive information (CodeQL #5157) #2163

Dumb question. I was told to fork the project and make a PR. I did that with https://github.com/thejrose1984/atmos/pull/1 but I'm assuming that means nothing because it won't actually do anything to make a PR against the source

@Andriy Knysh (Cloud Posse) this PR from @Igor Rodionov LGTM
https://github.com/cloudposse/atmos/pull/2263

@Andriy Knysh (Cloud Posse) this PR from @Ben Smith (Benbentwo) LGTM
https://github.com/cloudposse/atmos/pull/2144