#atmos - February 2022

@Erik Osterman (Cloud Posse) has joined the channel

@Lucky has joined the channel

@Leo Przybylski has joined the channel

@Ben Smith (Benbentwo) has joined the channel

@Max Lobur has joined the channel

@Steven Hopkins has joined the channel

@Hugo Samayoa has joined the channel

@Dan Meyers has joined the channel

@RB (pat leave again) has joined the channel

@Yonatan Koren has joined the channel

@Andy Miguel has joined the channel

@Maxim Mironenko (Cloud Posse) has joined the channel

@johncblandii has joined the channel

@Jeremy G has joined the channel

@Andriy Knysh (Cloud Posse) has joined the channel

@Matt Gowie has joined the channel

Good channel to have! 👍️

And congrats on Slack Pro!

@Imran Hussain has joined the channel

@Omry Hay has joined the channel

@Stewart Henderson has joined the channel

Slack Pro FTW!

@Matthew has joined the channel

@Mike Crowe has joined the channel

what is atmos?

can I run polumi with it ?

I’m looking for some guidance for the local usage of Atmos with cloudposse/stack-config/yaml (latest version) and terraform-provider-utils.

Since using the newer version, I’m running into issues where Atmos is not able to find its config easily and requiring me to symlink (or copy) the YAML file to atmos.yaml to ~/.atmos and additionally set ATMOS_BASE_PATH to the current directory otherwise the module won’t be able to find the stack config, because Terraform is executing within the component’s folder.

I’m not sure about configurability, but it would make sense to me to set that with Atmos before command execution. Unfortunately, my Go skills are more of the read-only variety, so I can’t really open a PR for that.

There a good cookiecutter repo for starting a new atmos-driven project by chance?

Where's the right (or best?) place to put workspace_key_prefix? I see examples with it in global.yaml, others with it in the components

hi there!

I'm just starting to learn Atmos but I already love the concept.

Is there any visual material I could look into? My brain doesn't cope well with fresh code, but i've been trough the Infrastructure as Code book so have solid grounds.

v1.3.27
🚀 Enhancements
Fix component path prefix if base component provided @aknysh (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1134415228" data-permission-text="Title is private" data-url="https://github.com/cloudposse/atmos/issues/120"...

Hello! Can this component be used (dns-primary) when I'm setting up a sub-domain (eg. subdomain.xyz.com) and the primary domain (eg. xyz.com) already exists and is being managed outside this stack?

Mineiros folks came out with their own Terraform Framework (similar to Atmos): https://github.com/mineiros-io/terramate

Interesting to check out.

v1.3.28
🚀 Enhancements
Fix Terraform workspace for remote state for derived components in subfolders @aknysh (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1145193302" data-permission-text="Title is private"...

1.3.28: Fix Terraform workspace for remote state for derived components in su…
…bfolders (#121)

Updates


Updates


Updates


Updates


Updates


Updates


Updates


Updates


Updates


Updates


Updates


Updates


Updates...

1.3.28
Fix Terraform workspace for remote state for derived components in su…

…bfolders (#121)

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Updates

* Auto Format

* Updates

* Auto Format

Co-authored-by:...

v1.3.29
what & why
Fix the failed releases
https://github.com/cloudposse/atmos/releases/tag/v1.3.28
https://github.com/cloudposse/atmos/releases/tag/1.3.28