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.

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

remove need to know vpn/vpn2 subnets by name #131

Open
thecaffiend opened this issue Oct 1, 2024 · 0 comments
Open

remove need to know vpn/vpn2 subnets by name #131

thecaffiend opened this issue Oct 1, 2024 · 0 comments
Labels
P1 Almost highest priority

Comments

@thecaffiend
Copy link
Contributor

thecaffiend commented Oct 1, 2024

We have a lot of places that need to know about the vpn/vpn2 subnets by name right now. That's not good as we shouldn't be beholden to specific names. Also, if we add another availability zone, we'd now have a vpn3 or something, and that would have to wired in in a lot of places.

One thing to consider is adding a type to each subnet and have special handling for known types (but don't require a type to be known to be created). So we could have "vpn" type that we cue off of, or "compute" or whatever.

@thecaffiend thecaffiend added the P1 Almost highest priority label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Almost highest priority
Projects
None yet
Development

No branches or pull requests

1 participant