## What issues it address?

#414

- Enabled VRF routes in Metal-cli.
- Improved metal gateways to support Vrf gateway inputs.

Co-authored-by: codinja1188 <3358152+vasubabu@users.noreply.github.com>

…and project id accordingly

Signed-off-by: Chris Privitere <23177737+cprivitere@users.noreply.github.com>

Signed-off-by: Chris Privitere <23177737+cprivitere@users.noreply.github.com>

Signed-off-by: Chris Privitere <23177737+cprivitere@users.noreply.github.com>

Signed-off-by: Chris Privitere <23177737+cprivitere@users.noreply.github.com>

… and projectid (#325)

#265

…eway (#433)

Fixes: #413

---------

Signed-off-by: Ayush Rangwala <ayush.rangwala@gmail.com>
Signed-off-by: Chris Privitere <23177737+cprivitere@users.noreply.github.com>
Co-authored-by: Chris Privitere <23177737+cprivitere@users.noreply.github.com>

…can time out instead of panic

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