Open brooksmtownsend opened 2 weeks ago
I can take this; please assign it to me.
Hello @brooksmtownsend, Does this look okay? If it does, then, I'll create the PR; otherwise let me know of any other improvements you'd like to see:
@ossfellow this looks wonderful! 😲
Affected project(s)
Is your feature request related to a problem? Please describe.
Looking at the inventory of hosts is one of the most common operations for
![image](https://github.com/wasmCloud/wasmCloud/assets/12040685/ae0d7f2b-1342-48b7-afe4-9157a4ebcff8)
wash
. However, when using file references or long generated component IDs, it becomes pretty unreadable.Taking a look at other infrastructure tools, like kubectl and nomad, none of them quite overflow the terminal like wash. I think this is largely due to the fidelity of information, and with wash displaying the full image reference really just isn't quite necessary.
Describe the solution you'd like
I would love for the host inventory to display just the right amount of information for the human readable format. Just like kubernetes, we can hide all of the other information behind the![image](https://github.com/wasmCloud/wasmCloud/assets/12040685/121bb53b-5c89-471c-b15a-d6aa4ba81fd7)
json
flag for when it's necessary.I propose that the host inventory display the following information:
I could even be convinced to drop the friendly name / host labels for the inventory operation, but it can be useful at a glance to verify that, for example, your application is spread properly across availability zones.
Describe alternatives you've considered
wash get hosts
command to keep the terminal more cleanAdditional context
No response