Skip to content

Conversation

@aayushsrivastava
Copy link

Description

Adds the ability to customize the tags for an individual NAT Gateway, NAT EIP, or private route table.

Motivation and Context

The components can have multiple instances in different AZs.

We are trying to import some existing VPC resources into Terraform. These resources have some tags that differ in value between AZs, and would like the Terraform module to be able to accomodate them.

Breaking Changes

No breaking changes

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have tested and validated these changes on an internal Terraform configuration at our company.
  • I have executed pre-commit run -a on my pull request

@github-actions
Copy link

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Sep 19, 2025
@bryantbiggs
Copy link
Member

thank you but this is not something we are going to accept at this time - tags should be standardized across resources and not so many unique/snowflake tags

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants