v2.0.0

Remove hardcoded providers to enable for_each/count @Benbentwo (#118)

## what

• Removed hardcoded provider "aws" configuration blocks from the module
• Added configuration_aliases to declare the expected provider aliases (aws.requester and aws.accepter)
• Updated example to define providers at the root level and pass them to the module via the providers argument
• Removed 13 provider-related variables that are no longer needed at the module level

why

This change enables the module to be used with for_each, count, and depends_on — meta-arguments that Terraform does not allow on modules containing provider configurations. Per Terraform's best practices, child modules should never configure providers directly; instead, they should declare configuration_aliases and expect the caller to provide pre-configured providers.

references

• Closes #48
• Closes #108
• Terraform Provider Configuration in Modules

🤖 Automatic Updates

Fix go version in tests @osterman (#111)

## what - Update go `1.24`

why

• Error loading shared library libresolv.so.2 in Go 1.20

References

• https://sweetops.slack.com/archives/G014YEKDH4K/p1746672149263629
• golang/go#59305 (comment)
• cloudposse/terraform-aws-cloudfront-s3-cdn#294

Replace Makefile with atmos.yaml @osterman (#110)

## what - Remove `Makefile` - Add `atmos.yaml`

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

v1.0.0

fix: use filtered subnet cidr blocks instead of the VPC cidr @bmbferreira (#83)

## what

This PR changes the module to start using the filtered subnet cidrs to create the routes, instead of using the whole VPC cidr.

why

Currently even when filtering the accepter or requester subnets by tags, the route table on the requester/accepter side is always created to the vpc cidr and doesn't create individual routes for each filtered subnet. This is not flexible enough as we might need for example peering to two different VPCs with overlapping CIDRs and we might want to use the subnet cidrs to be able to route to individual cidrs within the subnet, dodging the VPC cidr overlapping.

references

🤖 Automatic Updates

chore(deps): update terraform cloudposse/vpc/aws to v2.2.0 @renovate (#91)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/vpc/aws (source)	module	minor	2.1.0 -> 2.2.0

---

Release Notes

cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)

v2.2.0

Compare Source

v2.1.1

Compare Source

Add support for network address usage metrics @​lanzrein (#​124)

what

This PR adds support for Network Address Usage Metrics on the VPC.
AWS documentation : https://docs.aws.amazon.com/vpc/latest/userguide/network-address-usage.html
Terraform documentation : https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc#enable_network_address_usage_metrics

why

Network Address Usage metrics can help monitor the growth of a VPC and would be useful for any user.
Enable this after creating a VPC does not trigger recreation of the VPC.

references

closes #​115

Sync github @​max-lobur (#​120)

Rebuild github dir from the template

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​125)

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

v0.20.1

IPv6 communication over VPC peering @ngoyal16 (#101)

## what

Allow IPv6 communication b/w VPCs over VPC peering

why

Application hosted in VPC-1 wants to access resources hosted in private subnet of VPC-2 over IPv6.

references

Fix tests @goruha (#102)

## what * Fix tests

why

• Unblock community PRs

🤖 Automatic Updates

Migrate new test account @osterman (#100)

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

## 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 .github/settings.yml @osterman (#98)

## 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 .github/settings.yml @osterman (#97)

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

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

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

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

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

why

• Support new readme generation workflow.
• Generate banners

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

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

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

why

• Programmatically manage GitHub repo settings

Update Scaffolding @osterman (#88)

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

v0.20.0

what

• Remove of enabled part of the for_each ternary, as it disables assume_role on enabled = false, which blocks teardown

why

• local.enabled ternary causes no provider to be present on enabled = false, preventing teardown

v0.19.1

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

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

Replace deprecated data source 'aws_subnet_ids' @gberenice (#64)

what

• Data source aws_subnet_ids was replaced with aws_subnet for requester. This was already implemented for accepter.

why

• aws_subnet_ids has been deprecated and will be removed.

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/subnet_ids

v0.19.0

Revert PR #44 @Benbentwo (#62)

what

• Reverts PR #44 which introduced a bug when using default routing table

references

• Fixes #45
• Reopens #30

v0.18.0

feat: add configurable AWS route creation and deletion timeouts @morremeyer (#57)

what

• Adds configurable timeouts for AWS route creation and deletion

why

• Route creation and deletion can take longer than the provider defaults of 2m (creation) and 5m (deletion)

references

• Default timeouts set as they are in the provider, see https://registry.terraform.io/providers/hashicorp/aws/3.69.0/docs/resources/route#timeouts.
• Already implemented for terraform-aws-dynamic-subnets, this PR does the same for this module.

v0.17.1

🚀 Enhancements

Disable provider role assumption if enabled is false @nitrocode (#56)

what

• Disable provider role assumption if enabled is false

why

• Allow enabled = false

references

N/A

v0.17.0

Add `accepter_enabled` variable @aknysh (#52)

what

• Add accepter_enabled variable

why

• Allow provisioning only the requester side of the peering connection
• Useful in cases where the accepter side of the connection is managed manually

v0.16.2

🤖 Automatic Updates

Update context.tf @cloudpossebot (#55)

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.