\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

Create+attach:
$cgw_id = CreateCustomerGateway($type, $IP, $BgpAsn??) (radio button BGP/Static or just static?)->if static is allowed, users will need a way to edit routes
$vpn_id = CreateVpnGateway($type) $type = ipsec.1 (this step can happen whenever)
$vc_id = CreateVpnConnection($type, $cgw_id, $vpn_id) ->returns configuration info that the customer needs to know about to configure their customer gateway. Perhaps we have a row for this in the db and have a view VPN config button (disabled if VPN is not attached, enabled when it is), but then we couldn't have a 1:many relationship between VPCs and VPNs, as we should. Alternatively we could have a separate page for VPNs, or a modal for each VPC that displays the VPNs for that VPC(allows user to select a VPN and view info/status for it, delete it, etc.). Either way this will take some schema updates. Probably a new table called vpn.
AttachVpnGateway($vpn_id, $vpc_id) -> (only one vpc per vpn)

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Detach+delete:
DetachVpnGateway($vpn_id, $vpc_id)
DeleteVpnConnection($vc_id)
DeleteCustomerGateway($cgw_id)
DeleteVpcGateway($vpn_id)

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
May need to describe each of these to check states before attaching stuff to them.

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
VPNS HAVE LIMITS->need to have these disabled beyond dev.