@Erik Osterman (Cloud Posse) set the channel topic: Discussions related to https://github.com/cloudposse/docs
I think the docs need to be rebuilt
the code I just forked is right
yet the live page shows step 1 twice
Oh maybe I didn’t tag a release
We only redeploy on tagged release. Will set a reminder to check since I can’t do it my phone
will make notes of anything I see and wait for the next deploy before fixing in my fork
have a great thanksgiving yo
So with the cold-start docs I am updating the dockerfiles for root and testing. https://docs.cloudposse.com/reference-architectures/cold-start/
It occurs to me that it would be useful to have a list of all the resources that will be created, before any other steps, to help set context and scope
does this expect pre-existing dns or will a zone be created?
Im probably overthinking it
but I mean also if the cold start is creating the “non root” accounts how do you know the values of the testing account ID
I believe these are outputs
Collection of Terraform root module invocations for provisioning reference architectures - cloudposse/terraform-root-modules
not sure I follow
I have had a few beers
Update all ENV variables in the two Dockefiles in the repos with the values for your project: Change DOCKER_IMAGE Replace the namespace cpco with your own in all ENV vars Change the domain names from [cloudposse.co](http://cloudposse\.co) to your own In root, update the account ID (TF_VAR_account_id) to your own root account ID Change the IAM user names for the accounts Update the account emails
and opening the dockerfile in root they are
ENV TF_VAR_testing_account_id="126450723953" ENV TF_VAR_testing_name_servers='["[ns-312.awsdns-39.com>", "[ns-1416.awsdns-49.org>", "<http://ns-619.awsdns-13.net|ns-619.awsdns-13.net](http://ns\-1416\.awsdns\-49\.org)", "<http://ns-1794.awsdns-32.co.uk|ns-1794.awsdns-32.co.uk](http://ns\-312\.awsdns\-39\.com)"]'
Example Terraform Reference Architecture for Geodesic Module Parent (“Root” or “Identity”) Organization in AWS. - cloudposse/root.cloudposse.co
So I am pretty much stuck currently wondering why when I am at this point https://docs.cloudposse.com/reference-architectures/cold-start/# that I am getting
⧉ [root.aws.tf](http://root\.aws\.tf) ✓ (aws.tf-root-admin) iam ⨠ terraform plan -target=module.organization_access_group_root Acquiring state lock. This may take a few moments... var.audit_account_id Audit account ID
Despite having commented out all the env vars in the Dockerfile for root other than testing
directly after running
terraform plan -target=module.organization_access_group_root
yea ran through it all again carefully and ended up in the same pace
Unfortunately with the holidays won’t be able to really get my head into it until next week. We’re going to be on the road fri-sun.
@Andriy Knysh (Cloud Posse) can probably help tomorrow
Ah Yea mate, please do not feel obligated to do anything other than enjoy your holiday :)
ENV TF_VAR_testing_account_id= ENV TF_VAR_testing_name_servers=
Just noticed a typo
The [dev.cloudposse.co](http://dev\.cloudposse\.co) module represents an organization’s “development infrastructure”. This module is used as a sandbox environment where developers and test the waters and get familiar with AWS. We prescribe that organizations give all developers “Administrator” level privileges to this account where developers may test the waters.
his module is used as a sandbox environment where developers
something missing here? and test
Add the source_profile created in Step 2 to your ~/.aws/config.
step 2 refers to step 2 rather than step 1
can I just create merge requests fo these things?
Yes, totally! If you find anything like that would love help to correct it
awesome, im busy reading through all the docs, will make a pull request with em when done