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

This is improving the DX of a forth coming feature, which enables cross-repo minting of tokens

@Andriy Knysh (Cloud Posse) this fixes a confusing error when using atmos auth exec, where the command called is not found in the path. Atmos would say the subcommand was not found, but really it was the command executed was not found https://github.com/cloudposse/atmos/pull/2559

@Andriy Knysh (Cloud Posse) this allows --use-version without gh or GITHUB_TOKEN set. While the likely hood of hitting GitHub rate limits is greater, it shouldn't be a requirement.
https://github.com/cloudposse/atmos/pull/2212

@Andriy Knysh (Cloud Posse) this was verified by @Alexandre Feblot https://github.com/cloudposse/atmos/pull/2554

@Andriy Knysh (Cloud Posse) this fixes ATMOS_USE_VERSION env var https://github.com/cloudposse/atmos/pull/2556

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2231 this adds support for ECR public auth. It helps when hitting rate limits against public images on ECR

@Andriy Knysh (Cloud Posse) this is confirmed working by the person who opened the issues https://github.com/cloudposse/atmos/pull/2545

@Andriy Knysh (Cloud Posse) ✅️ LGTM https://github.com/cloudposse/atmos/pull/2549#pullrequestreview-4403739308

cc @Jonathan Rose

@Andriy Knysh (Cloud Posse) this fixes blog post date https://github.com/cloudposse/atmos/pull/2550

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

@Andriy Knysh (Cloud Posse) updated terragrunt migration guide https://github.com/cloudposse/atmos/pull/2527

@Jonathan Rose you are on a roll!

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

Concurrent execution is ready for first review. It is working for plan/apply/destroy, I'm stuck on how to run it in interactive mode 🤔

I can create TUI for that where end user will need to go through each component in a stack to review and approve/decline, or I can skip it for now and instead do the CI part where auto-approve is enabled

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

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2517 supports downloading all findings

@Andriy Knysh (Cloud Posse) a common failure I see in failed runs is 502 from the OpenTofu provider registry. This makes that a recoverable error.

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

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

this adds a .md for most documentation pages, as well as a Copy Markdown button (inspired by Vercel docs)

@Andriy Knysh (Cloud Posse) the new signature validation works well, but sometimes cosign has issues with something being malformed, causing tests to flap. But the good thing is we caught this before cutting a release. This PR makes it more robust, by retrying recoverable errors. Since it's very annoying when in CI toolchain installations fail for transient/recoverable errors.

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

@Andriy Knysh (Cloud Posse) this adds the new hooks support
https://github.com/cloudposse/atmos/pull/2482

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

cc @Alexandre Feblot

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

@Andriy Knysh (Cloud Posse) this hardens OCI pulls and improves messaging
https://github.com/cloudposse/atmos/pull/2487

@Andriy Knysh (Cloud Posse) this fixes a problem in main introduced by #2415
https://github.com/cloudposse/atmos/pull/2481

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

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

Guys, need your input on how to proper organise work on parallel execution DAG, without repository permission to create branches it's a bit messy now:

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

Also it will help to opt-in to stacked PRs if you're not already: https://github.github.com/gh-stack/

Anyway there are first findings described there on concurrency and current limitations when dealing with aliases that use same tf folder

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

@Andriy Knysh (Cloud Posse) added a pull request skill https://github.com/cloudposse/atmos/pull/2424 (since claude kept not labeling PRs)

@Andriy Knysh (Cloud Posse) this resolves the problem installing openbao https://github.com/cloudposse/atmos/pull/2414 reported by @Marat Bakeev

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

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

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

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

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

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

@Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/pull/2400 more algolia fixes

@Andriy Knysh (Cloud Posse) docs change that will hopefully fix the algolia search results.
https://github.com/cloudposse/atmos/pull/2393

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

@Igor Rodionov https://github.com/cloudposse/atmos/pull/2382 It's probably best to have you review this since you worked on this most recently.

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

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

Hey guys I have a PR that needs some love 😛
https://github.com/cloudposse/atmos/pull/2379

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

fix(jit): honor metadata.component subpath for JIT source-provisioned components by zack-is-cool · Pull Request #2371 · cloudposse/atmos

Needs a conceptual look probably, basically found that the metadata.component doesn't do anything with JIT/workdir and this is a proposed fix to that so it works similar to normal vendored components

Please review expanding unit tests to atmos

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

Question for you folks. Now that we can create components from upstream modules and even claude our own components, are ALL the cloudposse components still relevant and worth maintaining and creating new components? To push even further back, are there any modules that are so simple that aren't worth migrating to or using?

If any are flagged, will those repos be archived or will their readmes eventually be updated to use the newer/modern approach?

@Alexandre Feblot based on your findings, I pushed some updates to fix the provider aliases.
https://github.com/cloudposse/atmos/pull/2210

can you test with --use-version=2210

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