You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: