#atmos - December 2023

Hi folks, I'm trying out atmos (exciting times! 🚀) and have a few questions that I'm hoping you can help with:

1. How do I pass the outputs of one component as inputs to another? (within the same stack)
2. Does atmos automatically resolve dependencies? For example: say I have a stack with components A and B, with B taking the outputs of A as inputs. Component A changes and so do its outputs: can atmos redeploy B automatically? Similar question: does atmoshave a command to deploy all components in a stack?
3. Where can I find the full schema for stacks, workflows and the atmos.yaml file?
4. Do you know where I could find a production-ready repo that uses atmos?

Hi have couple of questions
1. The stack pattern {tenant}-{environment}-{stage}, is it possible to use different delimiters other than "-" because my stage or tenant names have dashes in them
2. How do I deploy all components in a stack with atmos command? workflow is the only option?

Hi few more questions
1. Atmos stacks could it be used with Terraform enterprise or any documentation with that regard about integration?
2. Could templates be used in stack configuration files

v1.51.0
what


Add examples/quick-start folder with an example infrastructure configuration


Update Quick Start docs


Add JSON Schema for Atmos manifests validation. Update atmos validate stacks to use the Atmos manifests validation JSON Schema. Update docs:

https://atmos.tools/reference/schemas/
<a href="https://atmos.tools/cli/commands/validate/stacks/"...

Will root components ever be available for brown field environments?

v1.51.0
what


Add examples/quick-start folder with an example infrastructure configuration


Update Quick Start docs


Add JSON Schema for Atmos manifests validation. Update atmos validate stacks to use the Atmos manifests validation JSON Schema. Update docs:

https://atmos.tools/reference/schemas/
<a href="https://atmos.tools/cli/commands/validate/stacks/"...

Hi Everyone,
Can some help me with account-map config or provide some good tutorial ?
I am new here trying to test the atmos tool on my local with my AWS account I was following the tutorial https://atmos.tools/category/quick-start
But now i am getting below error

using atmos one of my coworkers got this:

 Error: Plugin did not respond
│ 
│   with module.account_map.data.utils_component_config.config[0],
│   on .terraform/modules/account_map/modules/remote-state/main.tf line 1, in data "utils_component_config" "config":
│    1: data "utils_component_config" "config" {
│ 
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ReadDataSource call. The plugin logs may contain more details.

Guys, I'm trying to follow this tutorial and immediately after cloning git@github.com:cloudposse/tutorials.git, running atmos terraform plan fetch-location --stack=example gives:

invalid 'import' section in the file 'catalog/example.yaml' 

Hello. I’m wondering what is the best way to version Atmos terraform components? …

Are there any configs for tuning the auto-generated backend?

I am having an interesting issue with uid:gid mappings between the geodesic and the host. The status message at startup makes it look like everything will be fine.

# BindFS mapping of /localhost.bindfs to /localhost enabled.
# Files created under /localhost will have UID:GID 1047026499:1047000513 on host.

But doing anything w/ git results in errors:

│ Error: Failed to download module
│ 
│   on context.tf line 21:
│   21: module "this" {
│ 
│ Could not download module "this" (<http://context.tf:21|context.tf:21>) source code from "git::<https://github.com/cloudposse/terraform-null-label?ref=0.24.1>": error downloading '<https://github.com/cloudposse/terraform-null-label?ref=0.24.1>': /usr/bin/git exited with
│ 128: fatal: detected dubious ownership in repository at '/localhost/Development/atmos/tutorials/03-first-aws-environment/components/terraform/tfstate-backend/.terraform/modules/this'
│ To add an exception for this directory, call:
│ 
│ 	git config --global --add safe.directory /localhost/Development/atmos/tutorials/03-first-aws-environment/components/terraform/tfstate-backend/.terraform/modules/this
│ .

Is there any other atmos examples out there other than what's in the quick-start in the repo? I see there's a lot more validate tests for atmos and wondering if anyone has some to share

hey there, I'm using atmos with terraform 1.6.6 on darwin_arm64, and I'm getting this error every time I run my plan:

╷
│ Error: Failed to install provider
│ 
│ Error while installing hashicorp/template v2.2.0: the local package for <http://registry.terraform.io/hashicorp/template|registry.terraform.io/hashicorp/template> 2.2.0 doesn't match any of the checksums previously recorded in the dependency
│ lock file (this might be because the available checksums are for packages targeting different platforms); for more information: <https://www.terraform.io/language/provider-checksum-verification>
╵

In the past when I got this error in terraform (alone) I just went to the terraform folder and used https://github.com/kreuzwerker/m1-terraform-provider-helper to fix it, but this doesn't work with atmos. Do you know what I can do to fix it on atmos?

Hi, we're currently using atmos & cloudposse components to setup most of our infrastructure. We've setup an AWS Org with multiple accounts and two of those accounts have a VPC configured using the Cloudposse vpc component. I would now like to add vpc peering between these vpc's (which are in different regions). I am looking at the vpc-peering component documentation and see two use cases, peering v1 accounts to v2 accounts and v2 accounts to v2 accounts. What is the difference here and how do I know if my accounts are v1 or v2?

Is it possible to generate a dependency tree using atmos?

v1.52.0
what

Add additional and updated documentation for GitHub Actions with Atmos

why

GHA documentation was out-of-date