v0.17.0

Bc compliance @maximmi (#42)

what

• BridgeCrew compliance checks fix
• readme updated
• code clean up
• workflows updated
• default behaviour changed: is_multi_region_trail enabled by default

why

• To be able to position our modules as standards compliant
• Providing explicit note about policy attached directly to user
• removed unnecessary providers dependencies
• to stay in sync with all repos
• To comply BridgeCrew check

references

• https://docs.bridgecrew.io/docs/logging_1

v0.16.0

Terraform 0.14 upgrade @maximmi (#41)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.15.0

Terraform 0.14 upgrade @kevcube (#39)

what

update null label from 0.19.2 to latest

Release notes from 0.22.0:
Breaking change: This release updates minimum Terraform version requirement to 0.12.26

why

Needed to use this module on terraform 0.14 and null label 0.19.2 doesn't support that. If breaking compatibility with terraform 0.12.26 is undesirable then I can point to 0.21.0 of null-label.

v0.14.0

Update to `context.tf`. Update Terratest to Golang modules @aknysh (#36)

what

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

why

• Standardization and interoperability
• Keep the module up to date

0.13.1

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

0.12.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#34)

## 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.11.0: Updates to ChatOps - Automated commit (#33)

## What
* Adds chatops commands
  - '/test all'
  - '/test bats'
  - '/test readme'
  - '/test terratest'
* Drops codefresh
* Drops slash-command-dispatch
* Removes codefresh badge
* Rebuilds README

## Why
* Change over from codefresh to GH Actions
* Facilitate testing of PRs from forks

0.10.0 Use the latest label module to support the environment attribute

what

• Use the latest label module to support the environment attribute

why

• The environment attribute is useful for naming AWS resources

0.9.0

Rename KMS key (#28)

0.7.1

Rename KMS key (#27)