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.

v0.16.1

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.25.0 @renovate (#53)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	0.24.1 -> 0.25.0

---

Release Notes

cloudposse/terraform-null-label

v0.25.0

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @​Nuru (#​132)

##### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` ##### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #​131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @​korenyoni (#​130)

##### what * Update README snippets to reflect use of Terraform Registry. ##### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. ##### references * N/A

Bridgecrew compliance @​Nuru (#​125)

##### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` ##### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub ##### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

Properly output descriptors of chained modules @​Nuru (#​133)

##### what - Properly output descriptors of chained modules ##### why - Bug fix; implement intended behavior

---

Configuration

📅 Schedule: At any time (no schedule defined).

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

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 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 has been generated by WhiteSource Renovate. View repository job log here.

v0.16.0

Optional attribute variable @dmitriy-lukyanchikov (#46)

what

• add variable add_attribute_tag that will control creation of additional attribute accepted for accepted and requster for requester

why

This module can be used for creating cross-account and same account vpc peering. The case si next: if use dynamic aws creds in loop, but different attribute tag for accepted and the requester will conflict with each other for same account vpc peering. Also some time its not needed to add any additional attributes