Skip to content
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.

Sign up for GitHub

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

Jump to bottom

VPC 1.0 Usability: Change naming of subnets from 1, 2, 3 to match AZ? #913

Open
jkodroff opened this issue Sep 16, 2022 · 0 comments · May be fixed by #917
Open

VPC 1.0 Usability: Change naming of subnets from 1, 2, 3 to match AZ? #913

jkodroff opened this issue Sep 16, 2022 · 0 comments · May be fixed by #917
Labels
kind/enhancement Improvements or new features

Comments

@jkodroff
Copy link
Member

If we generate subnets with the default args, we name them, e.g. vpc-public-1, vpc-public-2, vpc-public-3. The names are more useful if we name them after the AZ they're in instead, e.g. vpc-public-1a, vpc-public-1b, vpc-public-1c.
@jkodroff jkodroff linked a pull request Sep 26, 2022 that will close this issue
Open
@mnlumi mnlumi added the kind/enhancement Improvements or new features label Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Improvements or new features
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Name subnets after the AZ they are deployed in. jkodroff/pulumi-awsx
2 participants
@jkodroff @mnlumi