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

secondary_ranges does not support subnets with the same name #107

Open
jhulndev opened this issue Nov 14, 2019 · 3 comments
Open

secondary_ranges does not support subnets with the same name #107

jhulndev opened this issue Nov 14, 2019 · 3 comments
Labels
enhancement New feature or request P3 medium priority issues triaged Scoped and ready for work

Comments

@jhulndev
Copy link

Since secondary_ranges is a map, it is not possible to utilize it if your subnets have the same name. In GCP the subnet names must be unique for a given region, this module should allow for the same.
@aaron-lane aaron-lane added the enhancement New feature or request label Nov 14, 2019
@morgante
Copy link
Contributor

I think we will fix this in #86.

@jhulndev jhulndev mentioned this issue Nov 15, 2019
Closed
@jhulndev
Copy link
Author

It looks like #69 could actually fix this as well.

@aaron-lane aaron-lane added P3 medium priority issues triaged Scoped and ready for work labels Dec 16, 2019
@omazin omazin assigned omazin and unassigned omazin Dec 19, 2019
@morgante morgante removed their assignment Apr 5, 2022
@imrannayer
Copy link
Collaborator

@jason-huling is it still an issue or should we close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request P3 medium priority issues triaged Scoped and ready for work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@morgante @jhulndev @aaron-lane @imrannayer @omazin