#geodesic - May 2021

RE: Atmos -- kudos to you @Joe Hosteny for your advice today in getting my Atmos compiles going. Everything works now. Cheers --

Hi all, I had some more time to work on our account conversion today. I got to the dns-primary component, but I seem to be missing something now. What is the expectation for how to run non-bootstrap terraform plan / apply for the non-bootstrap components using the terraform profiles, rather than the org role ARNs (I am looking at the all-new-components branch)? For example, it was easy for the iam-delegated-roles, as that component's provider performs an assume_role into the destination account. Is there a short blurb that gives a high level view of how things are to fit together?

Is tfstate now being saved only in in the root account even in a multi-account and multi-region setup? That is what I am understanding based on terraform-aws-components branch upstream-account-comps.

Is it possible to have multiple components based on the same component? Let’s say I wanted multiple vpcs defined in the same stack? I don’t want to create a unique root module direct for each vpc that duplicates the code.