v1.0.1

remove unused hashicorp/local provider @megashby (#66)

## what

• remove usage of hashicorp/local provider & update examples

why

• the hashicorp/local provider is not in use
• the hashicorp/local provider can be used to load files from local machine, when not intended this functionality can cause security concerns

references

🤖 Automatic Updates

Migrate new test account @osterman (#65)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

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

Update .github/settings.yml @osterman (#64)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

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

Update release workflow to allow pull-requests: write @osterman (#63)

## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PR

why

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

Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#62)

## what - Update workflows (`.github/workflows`) to use shared workflows from `.github` repo

why

• Reduce nested levels of reusable workflows

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#61)

## what - Update workflows (`.github/workflows`) to add `issue: write` permission needed by ReviewDog `tflint` action

why

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

Update GitHub workflows @osterman (#60)

## what - Update workflows (`.github/workflows/settings.yaml`)

why

• Support new readme generation workflow.
• Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#59)

## what

• Install latest GitHub Action Workflows

why

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

Add GitHub Settings @osterman (#58)

## what - Install a repository config (`.github/settings.yaml`)

why

• Programmatically manage GitHub repo settings

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

## 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

Update Scaffolding @osterman (#56)

## what - Reran `make readme` to rebuild `README.md` from `README.yaml` - Migrate to square badges - Add scaffolding for repo settings and Mergify

why

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

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

## 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

v1.0.0

Support AWS Provider V5 @max-lobur (#48)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Sync github @max-lobur (#46)

Rebuild github dir from the template

v0.11.0

• No changes

v0.10.0

Add/ignore cidr blocks @colinh6 (#43)

what

• This PR will introduce logic to ignore certain CIDR ranges from either the requestor or acceptor VPC(s), without affecting the existing functionality.

why

• We add the CIDR range 100.64.0.0/16 to each of our EKS cluster VPCs to increase the maximum amount of assignable IP addresses when using the AWS VPC CNI.
• This causes issues when attempting to leverage this existing peering module, as the 100.64.0.0/16 routes will conflict in certain cases.
• One specific case is where we want to peer and route a single database or elasticsearch VPC to multiple different EKS cluster VPCs that all contain the 100.64.0.0/16 additional CIDR association

references

• https://aws.amazon.com/premiumsupport/knowledge-center/eks-multiple-cidr-ranges/

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

v0.9.2

🚀 Enhancements

Remove unused and deprecated `template` provider @sapslaj (#37)

what

• Removes the template provider from required_providers

why

• The template provider is deprecated by Hashicorp.
• Said provider appears to be unused in this module (it works perfectly fine without it).
• Trying to run Terraform on an M1 Mac with this module results in an error since the template provider does not have a darwin_arm64 build.

references

• hashicorp/terraform-provider-template#85
• hashicorp/terraform#27257

v0.9.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#36)

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

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

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 #29

v0.8.0

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

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

Terraform 0.14 upgrade @maximmi (#28)

what

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

why

• Support Terraform 0.14

supersedes and closes #26

0.6.0: Allow filtering route tables using tags (#24)

what

• Caller can supply tags for both the acceptor and requestor VPCs, and if present, peering routes will only be added to route tables matching those tags.
• Default behavior is unchanged.

why

Support environments with private subnets that shouldn't be allowed to communicate with peer VPCs.