v0.8.0

• No changes

v0.7.2

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

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 (#22)

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 #19
• Closes #21
• Closes #17

v0.7.1

🚀 Enhancements

make github/init @nitrocode (#16)

what

• make github/init

why

• latest context with tenant

references

• Dependency of https://github.com/cloudposse/terraform-aws-datadog-lambda-forwarder

v0.7.0

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

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

🤖 Automatic Updates

Update context.tf @cloudpossebot (#12)

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

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

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

🚀 Enhancements

Terraform 0.14 upgrade @maximmi (#11)

what

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

why

• Support Terraform 0.14

v0.5.0

Support AWS 3.x @Nuru (#9)

what

• Breaking change: Take extra curl arguments as list of strings rather than single string. Should not have much impact as most users are probably using the default.
• Support AWS 3.x
• Convert required_providers from ~> to >=
• Update auto-release workflow to current

why

• Arguments must be in list form, this allows passing some number of arguments other than 1
• AWS 3 has features AWS 2 does not
• General policy is to not place upper bounds in order to facilitate testing
• Stay current

v0.4.0

Additional TF 0.13 Fixes @osterman (#8)

what

• upgrade chatops
• add automatic releasing
• upgrade to go modules
• update any version pinning
• (locally verififed) no terraform init errors using cli

why

• Support Terraform 0.13

0.3.0 Add `enabled` variable

what

• Add enabled variable

why

• We have enabled variable in all our modules
• When the module is used in other top-level modules with enabled variable present and set to false, this module needs to be disabled as well (otherwise it throws errors that it can't download the artifact)