why

• New test account uses modules.cptest.test-automation.app as test DNS zone

what

terraform-external-module-artifact 0.7.1 still relies on hashicorp/template which is not compatible with ARM.

0.8.0 is: cloudposse/terraform-external-module-artifact@0.7.1...0.8.0

why

hashicorp/template is not compatible with ARM64. The latest release of this module switched to template/cloudposse, but the external module that is called in lambda.tf still uses hashicorp/template in version 0.7.1. Upgrading to 0.8.0 solves this issue.

There are no breaking changes between 0.7.1 and 0.8.0.

references

cloudposse/terraform-external-module-artifact@0.7.1...0.8.0

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

why

• So we can support commenting on PRs with a link to the release

why

• Reduce nested levels of reusable workflows

why

• The ReviewDog action will comment with line-level suggestions based on linting failures

why

• Support new readme generation workflow.
• Generate banners

• Install latest GitHub Action Workflows

why

• Use shared workflows from cldouposse/.github repository
• Simplify management of workflows from centralized hub of configuration

why

• Programmatically manage GitHub repo settings

why

• Upstream template changed in the .github repo
• Work better with repository rulesets
• Modernize look & feel

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

• 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

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

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.

what

• Update terraform-external-module-artifact to 0.7.0

why

• Support latest context.tf

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

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

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

what

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

why

• Support Terraform 0.14