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?
metal vrf routes-create --vrf-id {vrf_id}
metal vrf routes-update --route-id {route_id}
metal vrf routes-get --route-id {route_id}
metal vrf routes-delete --route-id {route_id}
One of these two ids should probably be "id" as an argument. Use whatever the current convention is for subcommands with IDs and when we use the short "id" vs the subcommand prefix.
The text was updated successfully, but these errors were encountered:
## What issues it address?
#414
- Enabled VRF routes in Metal-cli.
- Improved metal gateways to support Vrf gateway inputs.
Co-authored-by: codinja1188 <[email protected]>
The test for the VRF route update subcommand was explicitly skipped. I
added a helper function to wait for the VRF route to be ready before
testing the update subcommand, but when the test was enabled it failed
because the subcommand was not capable of updating tags without updating
all other VRF route properties.
In addition to enabling the test for the VRF route update subcommand,
this updates the subcommand itself so that it only updates a VRF route
property if the user set the corresponding CLI flag.
Part of #414
What problem are you facing?
With #268 there are a few features of VRF yet to be implemented. Among them is VRF Routes configuration.
https://github.com/equinix-labs/metal-go/blob/main/docs/VRFsApi.md
How could the Equinix Metal CLI help solve this problem?
One of these two ids should probably be "id" as an argument. Use whatever the current convention is for subcommands with IDs and when we use the short "id" vs the subcommand prefix.
The text was updated successfully, but these errors were encountered: