Hi Stefan,
I’ve done some tests with the new Proxmox module and here are my first findings/thoughts:
-
Icons are cropped as the lines are not tall enough to accomodate them
-
Right now the same icon is used for qemu VMs and lxc containers
-
When using adhoc’s connection to the instance (SSH) it would be better to show the credential picker to select which one to use as the account used to connect to the Proxmox API may not be suitable for connecting
-
Tags display is not very easy to read
Maybe separating only with a semicolon without space didn’t help much
You could take a look at the cluster configuration api endpoint: /api2/json/cluster/options as it can provide customizations made and reflect what’s the Proxmox UI looks like:
{
"data": {
"tag-style": {
"shape": "full",
"ordering": "config",
"color-map": "2016:124882:FFFFFF;debian12:a64fb3:FFFFFF;2012r2:124882:FFFFFF;win10:124882:FFFFFF;centos7:b03721:FFFFFF;rocky8:b03721:FFFFFF;rocky9:b03721:FFFFFF;git:e78d0d:FFFFFF;lxc:3fc679:000000;fedora:387aff:ffffff;vl120:2e98b2:000000;vl130:006680:FFFFFF;vl140:dbb700:000000;vl150:640066:FFFFFF;vl50:994a00:FFFFFF;vl30:3d3bb5:FFFFFF;2022:124882:FFFFFF;win11:124882:FFFFFF;2012:124882:FFFFFF;debian13:a64fb3:FFFFFF;rocky10:b03721:FFFFFF;ubuntu22:ec7f1b:FFFFFF"
},
"allowed-tags": [
"2016",
"2022",
"debian12",
"debian13",
"fedora",
"git",
"lxc",
"rocky8",
"rocky9",
"tests",
"vl120",
"vl130",
"vl140",
"vl150",
"vl30",
"vl50",
"win10",
"win11"
]
}
}
The API only return overrides, so if a tag is set on a resource and is not in color-map, a default “neutral” display can be used, otherwise a simple bullet (
) or tag icon (
) using the overrided background color can be used 
Some tools do that: 
(ProxCenter) while some others don’t bother to fetch the colors and simply use a shape around the tag’s name: 
What do you think ?
Best Regards,
Nicolas.
