While figuring out naming conventions we discovered a quirk.
At the DC-level the names of security groups are displayed in all lower caps.
At the VM-level, when you apply those security groups, they display in the cap you entered them in.
Additionally, if you rename the SG name to uppercase the VM's reference is updated to the uppercase, but it becomes a "broken reference".
There is a bug report for v7 here, unsure the status: https://lists.proxmox.com/pipermail/pve-devel/2023-January/055596.html
As an, it would be useful to have an expanded character set / length for these group names:
current:
es_from_vpn
zbxagt_from_zbxsrv
preferred:
ELASTICSEARCH_from_VPN
ELASTICSEARCH<-VPN
zabbix_agent_from_zabbix_server
zabbix_agent <- zabbix_server
Are there any specific restrictions that would prevent the proxmox team from implementing these? I will submit a feature request, but want to make sure it's possible to implement these things before I do.
At the DC-level the names of security groups are displayed in all lower caps.
At the VM-level, when you apply those security groups, they display in the cap you entered them in.
Additionally, if you rename the SG name to uppercase the VM's reference is updated to the uppercase, but it becomes a "broken reference".
There is a bug report for v7 here, unsure the status: https://lists.proxmox.com/pipermail/pve-devel/2023-January/055596.html
As an, it would be useful to have an expanded character set / length for these group names:
current:
es_from_vpn
zbxagt_from_zbxsrv
preferred:
ELASTICSEARCH_from_VPN
ELASTICSEARCH<-VPN
zabbix_agent_from_zabbix_server
zabbix_agent <- zabbix_server
Are there any specific restrictions that would prevent the proxmox team from implementing these? I will submit a feature request, but want to make sure it's possible to implement these things before I do.
Last edited: