Skip to content

feat: Issue 1193 support for tagging subnets by name #1217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

voidshard
Copy link

@voidshard voidshard commented Jun 30, 2025

Description

Allows one to add per-subnet tags, settable by subnet name.

Motivation and Context

Currently it is possible to set tags on all subnets, or all subnets of a given distinction (eg. public, private, ..) but it is not possible to set tags on a given subnet. This is the motivation behind this issue and the related MR. This MR adds the same support for each subnet type rather than just public & private.

Breaking Changes

None

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 added my own simple example. It includes cases where all, none and a subset of subnets have custom tags added by name.

@voidshard voidshard changed the title 1193/support for tagging subnets by name feat/issue 1193 support for tagging subnets by name Jun 30, 2025
@voidshard voidshard force-pushed the 1193/Support_for_tagging_subnets_by_name branch from 5da956a to 55a871b Compare June 30, 2025 15:32
@voidshard voidshard force-pushed the 1193/Support_for_tagging_subnets_by_name branch from 55a871b to 9bd4853 Compare June 30, 2025 15:35
@voidshard voidshard changed the title feat/issue 1193 support for tagging subnets by name feat: issue 1193 support for tagging subnets by name Jun 30, 2025
@voidshard voidshard changed the title feat: issue 1193 support for tagging subnets by name feat: Issue 1193 support for tagging subnets by name Jun 30, 2025
@voidshard voidshard force-pushed the 1193/Support_for_tagging_subnets_by_name branch from 152d025 to 9ae1a79 Compare June 30, 2025 15:45
@voidshard
Copy link
Author

@antonbabenko @bryantbiggs please let me know your thoughts - we switched to using this module at work to define our VPCs but need a bit more flexibility to tag subnets appropriately for autodiscovery & configuration purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant