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
The first table header is empty when running metal capacity get without any [--options].
However, including an option will return all column headers, for examplemetal capacity get -m sv.
Thoughts
So the first column has no context that ml1 or ld7 refer to the data centers. And if we put a header there, then I suggest "DC" rather than "METRO" (because a 'DC' header works whether it's a metro or a facility).
Steps To Recreate
Deploy a server on console.equinix.com
Run command metal capacity get (the first column header will be empty)
Run command metal capacity get -m sv (all column headers will be populated)
How could the Equinix Metal CLI help solve this problem?
Perhaps leaving it empty was intended because LocationFieldin Line 92 refers to both Metros and Facilities, so as to avoid a metros/facilities header conflict in that first column (?).
Notes
I confirmed that all other get commands have table headers, some examples from Docs:
metal device get metal event get metal gateway get metal hardware-reservation get
So metal capacity get seems to be the only column header that returns empty.
Note
I submitted this as a feature instead of a bug because the empty header is not breaking anything.
CLI version (metal --version): metal version 0.24.0
What problem are you facing?
The first table header is empty when running
metal capacity getwithout any [--options].However, including an option will return all column headers, for example
metal capacity get -m sv.Thoughts
So the first column has no context that ml1 or ld7 refer to the data centers. And if we put a header there, then I suggest "DC" rather than "METRO" (because a 'DC' header works whether it's a metro or a facility).
Steps To Recreate
metal capacity get(the first column header will be empty)metal capacity get -m sv(all column headers will be populated)How could the Equinix Metal CLI help solve this problem?
Perhaps leaving it empty was intended because
LocationFieldin Line 92 refers to both Metros and Facilities, so as to avoid a metros/facilities header conflict in that first column (?).Notes
I confirmed that all other
getcommands have table headers, some examples from Docs:metal device getmetal event getmetal gateway getmetal hardware-reservation getSo
metal capacity getseems to be the only column header that returns empty.Note
I submitted this as a feature instead of a bug because the empty header is not breaking anything.
CLI version (
metal --version): metal version 0.24.0