From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
	by lore.proxmox.com (Postfix) with ESMTPS id 43B971FF146
	for <inbox@lore.proxmox.com>; Tue, 26 May 2026 10:10:03 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id CEEDA1576F;
	Tue, 26 May 2026 10:09:57 +0200 (CEST)
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Subject: applied: [PATCH pve-manager] ui: custom cpu model creation: restrict
 name field to valid IDs
Date: Tue, 26 May 2026 10:09:09 +0200
Message-ID: <177978294037.37648.9471965183086316505.b4-ty@proxmox.com>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20260521094928.260111-1-a.bied-charreton@proxmox.com>
References: <20260521094928.260111-1-a.bied-charreton@proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1779782939146
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.009 Adjusted score from AWL reputation of From:
 address
	BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment
	SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
	SPF_PASS               -0.001 SPF: sender matches SPF record
Message-ID-Hash: BB24CHF2NOFH36OPMURIW23DH3CDESUB
X-Message-ID-Hash: BB24CHF2NOFH36OPMURIW23DH3CDESUB
X-MailFrom: f.ebner@proxmox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; emergency; member-moderation; nonmember-moderation;
 administrivia; implicit-dest; max-recipients; max-size; news-moderation;
 no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

On Thu, 21 May 2026 11:49:28 +0200, Arthur Bied-Charreton wrote:
> 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.

Applied, thanks!

[1/1] ui: custom cpu model creation: restrict name field to valid IDs
      commit: 7e4a2f38833b8ede5c76295852f7d5e5a51943f7