v0.12.0

• No changes

v0.11.1

git.io->cloudposse.tools update @dylanbannon (#38)

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

🚀 Enhancements

Use cloudposse/template for arm support @nitrocode (#41)

what

• Use cloudposse/template for arm support

why

• The new cloudposse/template provider has a darwin arm binary for M1 laptops

references

• https://github.com/cloudposse/terraform-provider-template
• https://registry.terraform.io/providers/cloudposse/template/latest

• Closes #36

v0.11.0

fix: Adding environment variable @r351574nc3 (#35)

what

• Setting environment variable AWS_EC2_METADATA_DISABLED: true as a solution

why

• github actions is unable to push artifacts to s3 because of an error with the awscli.

references

• aws/aws-cli#5234 (comment)
• related to #13

v0.10.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#34)

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.10.0

Update Terraform cloudposse/module-artifact/external to v0.7.0 @htplbc (#30)

what

• Update terraform-external-module-artifact to 0.7.0

why

• Support latest context.tf

v0.9.0

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

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

Supersedes and closes #27
Supersedes and closes #28

v0.8.0

mfa_delete removed @maximmi (#26)

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.7.0

readme updated, BridgeCrew compliance checks fixed @maximmi (#25)

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: X-ray tracing mode for Lambda set to PassThrough
• 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
• https://docs.bridgecrew.io/docs/s3_13-enable-logging
• https://docs.bridgecrew.io/docs/s3_14-data-encrypted-at-rest

v0.6.1

🚀 Enhancements

Terraform 0.14 upgrade @maximmi (#22)

what

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

why

• Support Terraform 0.14

v0.6.0

Fix build @1efty (#18)

what

• Fixes build.
• Updates node used during build to v10.
• Adds --unsafe-perm=true and --allow-root

why

• When module is applied in it's current form, the artifacts that are pulled do not contain node_modules required for execution
• Updated node because it better aligns with lambda runtime support and adds support for --unsafe-perms=true and --allow-root which helps when using podman

references

#17