0.2.0

what

• Add variablemfa_delete

why

• This makes it possible to import a TF state backend bucket with mfa_delete enabled

Regenerate README.md

what

• Regenerate README.md

why

• Previous version of build-harness has some typos

Migrate to README.yaml format

what

• Add README.yaml

why

• Standardize README

0.1.1

what

• Make force_destroy a variable
• Make enable_server_side_encryption a variable

why

• For some stages (e.g. dev or test) we need to be able to destroy the bucket (even if it's not empty) when we destroy the environment with Terraform without manually deleting the objects in the bucket
• DynamoDB server-side encryption is currently not supported in some AWS regions (e.g. eu-west-3)

terraform apply

dynamodb_table_arn = arn:aws:dynamodb:eu-west-3:XXXXXXXXXX:table/cp-prod-terraform-state-lock
dynamodb_table_id = cp-prod-terraform-state-lock
dynamodb_table_name = cp-prod-terraform-state-lock
s3_bucket_arn = arn:aws:s3:::cp-prod-terraform-state
s3_bucket_domain_name = cp-prod-terraform-state.s3.amazonaws.com
s3_bucket_id = cp-prod-terraform-state

0.1.0

what

• Provision an S3 bucket needed to store terraform.tfstate file
• Provision a DynamoDB table to lock the state file

why

• To easily provision Terraform remote backend
• To lock the Terraform state file to prevent concurrent modifications and state corruption