v0.36.0

support type key for CodeBuild environment variables @joe-niland (#88)

what

• [BREAKING CHANGE] modify environment_variables variable to support the 'type' key
• Unless we change the type of the environment_variables variable to any and default 'type' to 'PLAINTEXT' this will be a breaking change, but a fairly easy one to deal with

why

• Adding the 'type' key allows sourcing env vars from SSM Parameter Store and Secrets Manager

references

• Closes #51

v0.35.0

feat: add support for optional S3 secondary artifact @jhosteny (#78)

Fixes #77.

what

• Adds an optional secondary artifact deployment to S3

why

• Allow the https://github.com/cloudposse/terraform-aws-ecs-web-app module to use the changes for a lightweight deployment of assets for an S3-backed CDN

references

Closes #77

v0.34.0

Integrated the changes from dome9 @bcoddens (#86)

What
Our codebuild environment needs double sources as input to build
Why
We use code that is based on gitlab , gitlab is not supported by codebuild so we need to upload zip files to support our codebuilds. We want to keep the config and source in a different upload.
These changes support using multiple s3 buckets as source
References
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/codebuild_project#secondary_sources
Proceed on pull request: #73

v0.33.0

Add IAM policy permissions to allow CodeBuild to run in a VPC @joe-niland (#84)

what

• Update IAM permissions in Codebuild policy to allow running in a VPC
• Add a test using VPC config
• Change test region to us-east-2
• (There is probably a more elegant way to check if var.vpc_config is an empty object but I didn't find one in the time I spent looking.)

why

• The module supported setting VPC config on the Codebuild project, but the IAM permissions in the Codebuild policy were not sufficient

references

• None

v0.32.0

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#83)

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.31.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#80)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.31.0

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#82)

what

• update context.tf to v0.23.0
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.30.1

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#81)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.30.0

mfa_delete removed due to issue in terraform @maximmi (#79)

what

• mfa_delete removed
• Bridgecrew check Ensure S3 bucket has MFA delete enabled skipped

why

• Because terraform doesn't support this argument to be toggled (hashicorp/terraform-provider-aws#629).
• To satisfy Bridgecrew compliance scan

references

• hashicorp/terraform-provider-aws#629

v0.29.0

readme updated, BridgeCrew compliance checks fixes, code cleaned @maximmi (#75)

what

• BridgeCrew compliance checks fix
• readme updated
• default behaviour changed: S3 bucket MFA delete enabled by default
• default behaviour changed: S3 Bucket Versioning enabled by default
• default behaviour changed: Encryption of the S3 bucket enabled by default

why

• To be able to position our modules as standards compliant
• stay in sync with code
• To comply BridgeCrew check

references

• https://docs.bridgecrew.io/docs/s3_16-enable-versioning
• https://docs.bridgecrew.io/docs/s3_13-enable-logging
• https://docs.bridgecrew.io/docs/s3_14-data-encrypted-at-rest