What happened?
When we create a vrf currently, we get the following output:
❯ metal vrf create -m ch -r 192.168.1.1/29 -a 12003 -n testvrf
+---------+------+-------------+----------------+-------------------------------+---------+
| ID | NAME | DESCRIPTION | LOCALASN | IPRANGES | CREATED |
+---------+------+-------------+----------------+-------------------------------+---------+
| testvrf | | 12003 | 192.168.1.0/29 | 2024-01-19 20:33:52 +0000 UTC |
+---------+------+-------------+----------------+-------------------------------+---------+
If you wait a sec and then run a get, you get something like this
+--------------------------------------+---------+-------------+----------------+----------+-------------------------------+
| ID | NAME | DESCRIPTION | IPRANGES | LOCALASN | CREATED |
+--------------------------------------+---------+-------------+----------------+----------+-------------------------------+
| 5ee64f98-fa3d-47f8-83c9-273dd7298147 | testvrf | | 192.168.1.0/29 | 12003 | 2024-01-19 20:33:52 +0000 UTC |
+--------------------------------------+---------+-------------+----------------+----------+-------------------------------+
Ideally, the initial output should look more like the latter, at least putting fields in the right columns if we don't have all the info yet.
How can we reproduce it?
Make a vrf with metal vrf create
CLI version (metal --version): 0.19.0
What happened?
When we create a vrf currently, we get the following output:
If you wait a sec and then run a get, you get something like this
Ideally, the initial output should look more like the latter, at least putting fields in the right columns if we don't have all the info yet.
How can we reproduce it?
Make a vrf with
metal vrf createCLI version (
metal --version): 0.19.0