From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 4DAFC1FF146 for ; Tue, 26 May 2026 15:50:51 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id ECE1BA39; Tue, 26 May 2026 15:50:49 +0200 (CEST) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Lukas Wagner Subject: applied: [PATCH datacenter-manager] api: autoinstaller: token: enforce token schema constraints Date: Tue, 26 May 2026 15:50:07 +0200 Message-ID: <177980340432.2236806.17496026278746188445.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260526133056.334639-1-l.wagner@proxmox.com> References: <20260526133056.334639-1-l.wagner@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: 1779803391818 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.005 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: VS3Y2D7WPLQCKTBQQG3C27LA3ZMZKCAW X-Message-ID-Hash: VS3Y2D7WPLQCKTBQQG3C27LA3ZMZKCAW X-MailFrom: t.lamprecht@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 Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 26 May 2026 15:30:56 +0200, Lukas Wagner wrote: > The PROXMOX_TOKEN_NAME schema is already used internally in the id > property of the AnswerToken type, so it makes sense to propagate the > schema to the API handler as well. Applied, thanks! [1/1] api: autoinstaller: token: enforce token schema constraints commit: 9c10578b262c54ad20ca53525cc5f9a16506f50b