0.8.0 Convert to TF 0.12. Add tests. Add Codefresh test pipeline

what

• Port module to Terraform 0.12
• Pin all providers
• Add example for testing
• Add bats and terratest for the example
• Add Codefresh badge to point to the test pipeline in terraform-modules project
• Update README

why

• Module currently does not work with 0.12. Much easier syntax
• Better regression control
• Automatically test the example on every commit and pull request
• Provision resources on AWS in the test account and check the outputs for the correct values
• terraform-modules project contains pipelines for all terraform modules

0.7.0 Add "enabled" flag

what

• Add "enabled" flag

why

• Enable/disable creating all module's resources

0.6.0 Add variable `is_organization_trail`

what

• Add variable is_organization_trail

why

• This is an update to use the new argument is_organization_trail for the resource aws_cloudtrail

0.5.0

what

Change the event_selector var from a map to a list type.

why

It is currently a type map, that then gets put inside a list.
Even though it is a null map by default, because it is embedded into a list, it is evaluated by the cloudtrail resource.
And because it gets evaluated by the resource it triggers this bug:
hashicorp/terraform-provider-aws#5448

By switching it to a list, it means that by default instead of being a mull map in a null list, it is just a null list. Which is skipped over, and doesn't trigger the bug.

TF Apply with the Cloudtrail module always comes up with :

~ module.cloudtrail.aws_cloudtrail.default
     event_selector.#:                           "0" => "1"
     event_selector.0.include_management_events: "" => "true"
     event_selector.0.read_write_type:           "" => "All"

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.4.0: Add cloudwatch logs (#7)

* Added missing variables to cloudtrail

* Updated fields, and changed to terraform-terraform-label

0.3.1

what

Fix typo

0.3.0

what

Accept external S3 bucket

why

The bucket could be from the same ASW account or from a different account.

This is useful if an organization uses a number of separate AWS accounts to isolate the Audit environment from other environments (production, staging, development).

In this case, you create CloudTrail in the production environment (production AWS account),
while the S3 bucket to store the CloudTrail logs is created in the Audit AWS account, restricting access to the logs only to the users/groups from the Audit account.

0.2.0

what

• Use terraform-aws-s3-log-storage module for CloudTrail logs
• Add TravisCI

why

• terraform-aws-s3-log-storage provisions an S3 bucket with server-side encryption, versioning and life-cycle events (to move the logs to Glacier), which is what's required for CloudTrail logs
• Reuse code
• TravisCI to lint Terraform code and monitor build status