0.22.0

[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.21.0: Revert 0.19.0 (#56)

## what
* Reverts the updates from #53 as they were no good. 

## why
* Using the flag to not write the back config file causes terraform to believe the file should be destroyed since it was no longer tracked as a resource. That approach just generally won't work. 

## references
* Reverts #53

0.20.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#55)

## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

0.19.0: Adds check to only write backend config file if path doesn't exist

what

• This allows users to edit the backend config file once written and not have to worry about it being overwritten by the module due to changes.

why

• Any changes to the backend.tf file are overwritten on the next apply, which can be annoying if trying to specify additional required_providers, required_version, or other terraform configuration block changes. This updates the template file block so that file is not overwritten if the backend.tf (or other terraform config file name) already exists.

0.18.2: Fixes terraform destroy

what

• Add the missing empty string list to coalesce() call

why

• Without this fix, issue #51 arises for terraform 0.12 destroy

references

• hashicorp/terraform#21370
• terraform-aws-modules/terraform-aws-ec2-instance#104
• Closes #51
• #52

0.18.1: Enhance README w/ info on outputting terraform.tf

what

• Add terraform.tf to the usage instructions

why

• The current usage does not account for terraform.tf, which is actually quite brilliant functionality

references

• #46

0.18.0 Make the S3 Bucket Public Access Block optional

what

• Make the S3 Bucket Public Access Block optional (#48)

why

• Allows use of this module without being required to create the public access block resource

0.17.0 Bump label module to 0.16.0

what

• Bump label module to 0.16.0

why

• to avoid null_data_source "count cannot be computed" errors

0.16.0 Extend S3 bucket policy to ensure encryption-in-transit

what

• This change extends the S3 bucket policy to enforce encryption in
  transit

why

• Whilst the current option policy ensures server-side encryption,
  encryption of the transport mechanism isn't enforced.

refs

• https://docs.aws.amazon.com/config/latest/developerguide/s3-bucket-ssl-requests-only.html

0.15.0 Set appropriate AWS ARN for S3 bucket policies in GovCloud

What

• Parameterize the ARN prefix used for S3 bucket policies such that if we are deploying in an AWS GovCloud region, the ARN prefix is arn:aws-us-gov:s3. Otherwise, the ARN prefix is arn:aws:s3.

Why

• These changes allow successful deployment in GovCloud (tested in us-gov-west-1). Prior to this change, attempting to deploy in GovCloud would fail with:

Error: Error putting S3 policy: MalformedPolicy: Policy has invalid resource status code: 400

References

• https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/using-govcloud-arns.html