* [PATCH pve-manager] ui: custom cpu model creation: restrict name field to valid IDs
@ 2026-05-21 9:49 Arthur Bied-Charreton
0 siblings, 0 replies; only message in thread
From: Arthur Bied-Charreton @ 2026-05-21 9:49 UTC (permalink / raw)
To: pve-devel
Until now, the frontend would let invalid PVE config IDs through only
for them to be rejected by the backend.
Reflect the backend format restriction (pve-configid) in the UI by
adding the ConfigId vtype to the name field of the custom CPU model
creation window.
Reported-by: Christian Ebner <c.ebner@proxmox.com>
Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
---
www/manager6/dc/CPUTypeEdit.js | 1 +
1 file changed, 1 insertion(+)
diff --git a/www/manager6/dc/CPUTypeEdit.js b/www/manager6/dc/CPUTypeEdit.js
index 1b56686a..904b50d5 100644
--- a/www/manager6/dc/CPUTypeEdit.js
+++ b/www/manager6/dc/CPUTypeEdit.js
@@ -52,6 +52,7 @@ Ext.define('PVE.dc.CPUTypeEdit', {
editable: '{isCreate}',
value: '{cputype}',
},
+ vtype: 'ConfigId',
name: 'cputype',
maxLength: 40,
renderer: (val) => val.replace(/^custom-/, ''),
--
2.47.3
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2026-05-21 9:49 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-21 9:49 [PATCH pve-manager] ui: custom cpu model creation: restrict name field to valid IDs Arthur Bied-Charreton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox