Terraform Aws Kms Key Versions Save

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

what

• Provider bump

why

• Prevent stale .terraform directories from preventing planning this module

references

• https://github.com/cloudposse/terraform-aws-kms-key/pull/30

what

• Provider bump

why

• Prevent stale .terraform directories from preventing planning this module

references

• https://github.com/cloudposse/terraform-aws-kms-key/pull/30

what

• Add multi_region

why

• for keys that need to be used cross region
• note this change will require 3.64.0 provider going forward

references

• https://aws.amazon.com/about-aws/whats-new/2021/06/kms-multi-region-keys/
• https://github.com/hashicorp/terraform-provider-aws/releases/tag/v3.64.0

what

• Update context.tf to that of null-label:0.25.0
• Run make github/init.
• drop Terraform 0.12 support.

why

• The auto-context job was disabled because this repository was inactive for 90 days. This manually updates context.tf as it allows for the new tenant label.
• make github/init updates GitHub Actions Workflow files to their latest reference counterparts.
• validation rules were introduced in Terraform 0.13 and are used in the latest context.tf distribution. This PR drops support for Terraform 0.12 and below in order to enable updating to the latest context.tf distribution.

references

• https://github.com/cloudposse/terraform-null-label/releases/tag/0.25.0

what

• Added optional variables key_usage and customer_master_key_spec
• Updated GitHub configs

why

• To be able to use the created KMS key with DNSSEC in Route53. The defaults remain unchanged.

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/kms_key#key_usage
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/kms_key#customer_master_key_spec

what

• workflows update
• TF required_version reduced to 0.12.26

why

• to use most recent automatisation for repo
• for backward compatibility

what

• Update to context.tf
• Update Terratest to Golang modules

why

• Standardization and interoperability
• Keep the module up to date