0.3.2

what

• Add projects for testing stage

why

• To have an account to quickly create and destroy infrastructure for testing

0.3.1

what

• Add audit-cloudtrail project

why

• Move it from the audit stage repo
• Keep all reference architecture modules in terraform-root-modules

0.3.0

what

• Add projects (dns and iam) from root stage (and eliminate dependencies of those projects on terraform-account-metadata)
• Add accounts project

why

• Keep all reference architecture modules in one repo
• Provision member accounts (prod, staging, dev, audit) in an organization

0.2.1

what

• Add organization project

why

• To easily create an AWS Organization from the master account

0.2.0

what

• Remove dependencies on terraform-aws-account-metadata
• Use Terraform vars instead (which could be be provided from Dockerfile or chamber)

why

• Maketerraform-root-modules a generic Terraform module that could be used for different projects (including third-party) and for Cloud Posse documentation
• terraform-aws-account-metadata is a private repo and contains secrets
• Eliminate cold-start cycles
• Fewer repos to maintain

0.1.5

Update external-dns.tf (#7)

0.1.4

what

• Update README to CloudPosse standard README.md format

why

• Standard documentation
• Consistency

0.1.3

Push to `cloudposse` Registry (#4)

0.1.2: Push stable images to dockerhub (#3)

* push to dockerhub

* Use scratch image

0.1.1: Merge main and output (#2)

* Merge main and output

* Fix structure

* Rename chamber structur