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
How could the Equinix Metal CLI help solve this problem?
At first glance, it looks like these are the commands one would expect:
metal connection create [--organization-id {organization_id} | --project-id {project_id}] [args] # createOrganizationInterconnection, createProjectInterconnection
metal connection list [--organization-id {organization_id} | --project-id {project_id}] # organizationListInterconnections, projectListInterconnections
metal connection -i {connection_id} get # getInterconnection
metal connection -i {connection_id} delete # deleteInterconnection
metal connection -i {connection_id} update [args] # updateInterconnection
metal connection -i {connection_id} --port-id {port_id} create-virtual-circuit [--vlan] [args] # createInterconnectionPortVirtualCircuit
metal connection -i {connection_id} --port-id {port_id} create-virtual-circuit [--vrf] [args] # createInterconnectionPortVirtualCircuit
metal connection -i {connection_id} list-ports # listInterconnectionPorts
metal connection -i {connection_id} --port-id {port_id} get-port # getInterconnectionPort
metal connection -i {connection_id} --port-id {port_id} list-virtual-circuits # listInterconnectionPortVirtualCircuits
metal virtual-circuit -i {vc_id} get # getVirtualCircuit
metal virtual-circuit -i {vc_id} update [args] # updateVirtualCircuit
metal virtual-circuit -i {vc_id} delete # deleteVirtualCircuit
create-virtual-circuit could be designed to take --vlan and --vrf to discriminate between
VlanVirtualCircuitCreateInput and VrfVirtualCircuitCreateInput, or this could be baked into the subcommand name: create-vlan-virtual-circuit / create-vrf-virtual-circuit.
Aliases:
connection whould have an alias of interconnection and conn
virtual-circuit would have an alias of vc
Perhaps: list-virtual-circuits could have aliases? list-port-virtual-circuits, list-vcs. Same for create-virtual-circuit.
Connection resources are important to VRF users, and vice-versa. Relates to #268
The text was updated successfully, but these errors were encountered:
displague
changed the title
Add support for Metal Interconnections
Add support for Metal Interconnections and VirtualCircuits (for VLANs and VRF)
Dec 15, 2023
- [ ] Enabled virtual-circuit subcommands in metal-cli
- [ ] Improved Virtual network E2E test cases as per new cases
Part of #307
Co-authored-by: Vasubabu <[email protected]>
What problem are you facing?
It is not possible to list, create, get, delete, or update connections or virtual-circuit resources through the Metal CLI.
These resources are described in:
How could the Equinix Metal CLI help solve this problem?
At first glance, it looks like these are the commands one would expect:
create-virtual-circuit
could be designed to take--vlan
and--vrf
to discriminate betweenVlanVirtualCircuitCreateInput and VrfVirtualCircuitCreateInput, or this could be baked into the subcommand name:
create-vlan-virtual-circuit
/create-vrf-virtual-circuit
.Aliases:
connection
whould have an alias ofinterconnection
andconn
virtual-circuit
would have an alias ofvc
list-virtual-circuits
could have aliases?list-port-virtual-circuits
,list-vcs
. Same forcreate-virtual-circuit
.Connection resources are important to VRF users, and vice-versa. Relates to #268
The text was updated successfully, but these errors were encountered: