#atmos - September 2023

v1.45.0
what
Add dependencies on external files and folders to settings.depends_on
Fix context inheritance in Atmos imports with Go templates with Multiple inheritance
Add/update docs
why

Add dependencies on external files and folders to settings.depends_on. Allow specifying that an Atmos component depends on external files or folders. When the files or folders are modified, the command atmos describe affected will detect that and include the dependent component to the affected output list. This is...

v1.45.0
what
Add dependencies on external files and folders to settings.depends_on
Fix context inheritance in Atmos imports with Go templates with Multiple inheritance
Add/update docs
why

Add dependencies on external files and folders to settings.depends_on. Allow specifying that an Atmos component depends on external files or folders. When the files or folders are modified, the command atmos describe affected will detect that and include the dependent component to the affected output list. This is...

v1.45.1
What's Changed
Update Secret Reference to Fix Brew workflow by @Benbentwo in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1886167524" data-permission-text="Title is private"...

v1.45.1
What's Changed
Update Secret Reference to Fix Brew workflow by @Benbentwo in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1886167524" data-permission-text="Title is private"...

v1.45.2
What's Changed
Bugfix: formula-path for Promoting to homebrew by @Benbentwo in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1886299079" data-permission-text="Title is private"...

v1.45.3
What's Changed
Bugfix: formula-path for Promoting to homebrew by @Benbentwo in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1886299079" data-permission-text="Title is private"...

v1.45.3
What's Changed
Bugfix: formula-path for Promoting to homebrew by @Benbentwo in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1886299079" data-permission-text="Title is private"...

Only quite new to Atmos, trying to get aquinted with all of the concepts and way of working. Starting to get an understanding. However, comparing root modules of something like vpc with sqs and ecr, I am not sure what the best practises are dealing with:
• situation of setting up different similar infra eg. different buckets, couple queues. If you have a lot of queues or buckets seems odd/cumbersome to have to deploy every queue separate? In this way, ECR is really easy and clean. Is it then recommended to setup a workflow for all buckets/queues?
• Thinking about “Encapsulation”, sqs + sqs dlq would probably need to be in the same component? I see there is no support yet for this in cloudposse/terraform-aws-components

Atmos makes it easy to move around components, but stacks itself not so much. For good reason as normally you should not need to change namespace or tenant, but what if you do? Is there a less painful way of doing this in bulk?

In the Spacelift Spaces Atmos yaml is it possible to utilize body or body_url to reference a file in the repository? The url approach is less fun out of a private repo.

Hi folks, I can’t seem to find any reference on Atmos stack destruction or any deletion in particular. What would be the recommended “elegant” way of deleting every resource about and in specific AWS account. The stacks were created using Spacelift with Atmos.

Hi Folks
I just got acquainted with atmos … where is the best place to start my upskilling journey

So thinking out loud here.. I am building a monorepo using atmos to handle a basic digital ocean infrastructure. I have some post instance configuration to automate with ansible as it’s a bit clunky to try to achieve in user-data. Is there a preferred way to have atmos run an ansible playbook that can hook into terraform state outputs to populate its inventory? Or would this be territory for some atmos custom commands? Right now I just have a task yaml in components/ansible/playbook.yaml

Hey folks! First and foremost — thanks for this amazing tool and general positive influence on the Terraform community 💪

Q: Is it possible to use atmos purely to synthesise the final stack folder with all the requires *.tf files & configured backend, but without running the init, plan or any other command? The desired effect I'm searching for is pretty much what what terramate create does.

I know there's:
• atmos terraform generate backend
• atmos terraform generate varfile
• atmos terraform shell
But none of these seem to do what I want. Correct me if I'm wrong.

Thanks! 🙂