Is your feature request related to a problem? Please describe.
Using the new per-guest summary it's hard to tell which ID refers to which guest.
Describe the solution you'd like
Using the per-guest summary as example this
/ns/pbs/ct/100 : 1.2GiB (1322780915 B)
/ns/pve/vm/125 : 1.0GiB (1118879268 B)
/ns/pve/ct/303 : 994.9MiB (1043184797 B)
could look like this
/ns/pbs/ct/100 (somenamehere) : 1.2GiB (1322780915 B)
/ns/pve/vm/125 (someothernamehere) : 1.0GiB (1118879268 B)
/ns/pve/ct/303 (yetanothernamehere) : 994.9MiB (1043184797 B)
This can be shown in the interactive selector and such as well, of course.
📂 Current path: /ns/NAMESPACEHERE/ct
> Use current path
.. (up one level)
100/ | somenamehere
It might make sense to limit the length and/or only grab the comment up to the first space or similar in case the default {{guestname}} changed.
Additional context
An example command that would print the comment for a ID could look like this
proxmox-backup-debug api get /admin/datastore/DATASTOREHERE/snapshots --ns NAMESPACEHERE --output-format json | jq -r 'map(select(.["backup-id"] == "IDHERE")) | .[-1].comment'
It feels kind of inelegant but I couldn't find a better way to extract this information and this is what the GUI uses.
Is your feature request related to a problem? Please describe.
Using the new per-guest summary it's hard to tell which ID refers to which guest.
Describe the solution you'd like
Using the per-guest summary as example this
could look like this
This can be shown in the interactive selector and such as well, of course.
It might make sense to limit the length and/or only grab the comment up to the first space or similar in case the default
{{guestname}}changed.Additional context
An example command that would print the comment for a ID could look like this
It feels kind of inelegant but I couldn't find a better way to extract this information and this is what the GUI uses.