#docs (2018-11)

Discussions related to https://github.com/cloudposse/docs

Archive: https://archive.sweetops.com/docs/

2018-11-30

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
11:33:58 PM

@Erik Osterman (Cloud Posse) set the channel topic: Discussions related to https://github.com/cloudposse/docs

2018-11-22

Jan avatar

mmmm

Jan avatar

I think the docs need to be rebuilt

Jan avatar

the code I just forked is right

Jan avatar
Jan
04:21:06 PM
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Can you share a direct link

Jan avatar

yet the live page shows step 1 twice

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Oh maybe I didn’t tag a release

Jan avatar

:–1:

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

We only redeploy on tagged release. Will set a reminder to check since I can’t do it my phone

Jan avatar

cool cool

Jan avatar

will make notes of anything I see and wait for the next deploy before fixing in my fork

Jan avatar

have a great thanksgiving yo

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

thanks @Jan

Jan avatar

:–1:

Jan avatar

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

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Yea, makes sense…

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

so something like:

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

“After completing the following steps you will have: 1) … 2)… 3)…”

:--1:1
Jan avatar

in the sense that im not sure for example “Select the parent DNS domain name for your infrastructure - in these examples we use cloudposse.co

Jan avatar

does this expect pre-existing dns or will a zone be created?

Jan avatar

Im probably overthinking it

Jan avatar

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

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

I believe these are outputs

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
cloudposse/terraform-root-modules

Collection of Terraform root module invocations for provisioning reference architectures - cloudposse/terraform-root-modules

Jan avatar

not sure I follow

Jan avatar

I have had a few beers

Jan avatar

but…

Jan avatar
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
Jan avatar

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)"]'
Jan avatar
cloudposse/root.cloudposse.co

Example Terraform Reference Architecture for Geodesic Module Parent (“Root” or “Identity”) Organization in AWS. - cloudposse/root.cloudposse.co

Jan avatar

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

Jan avatar

directly after running terraform plan -target=module.organization_access_group_root

Jan avatar

yea ran through it all again carefully and ended up in the same pace

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

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.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@Andriy Knysh (Cloud Posse) can probably help tomorrow

Jan avatar

Ah Yea mate, please do not feel obligated to do anything other than enjoy your holiday :)

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Jan avatar
ENV TF_VAR_testing_account_id=
ENV TF_VAR_testing_name_servers=

2018-11-19

Jan avatar

Hola

Jan avatar

Just noticed a typo

Jan avatar
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.
Jan avatar

his module is used as a sandbox environment where developers something missing here? and test

Jan avatar
Add the source_profile created in Step 2 to your ~/.aws/config.

step 2 refers to step 2 rather than step 1

Jan avatar

can I just create merge requests fo these things?

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Yes, totally! If you find anything like that would love help to correct it

Jan avatar

awesome, im busy reading through all the docs, will make a pull request with em when done

    keyboard_arrow_up