From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id AAEE61FF184 for ; Thu, 4 Dec 2025 15:17:20 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B3F3415B4; Thu, 4 Dec 2025 15:17:47 +0100 (CET) Mime-Version: 1.0 Date: Thu, 04 Dec 2025 15:17:45 +0100 Message-Id: From: "Lukas Wagner" To: "Proxmox Datacenter Manager development discussion" , "Christoph Heiss" X-Mailer: aerc 0.21.0-0-g5549850facc2-dirty References: <20251204125122.945961-1-c.heiss@proxmox.com> In-Reply-To: <20251204125122.945961-1-c.heiss@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1764857818625 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.118 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 POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pdm-devel] [PATCH proxmox/datacenter-manager 00/13] initial auto-installer integration X-BeenThere: pdm-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Datacenter Manager development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pdm-devel-bounces@lists.proxmox.com Sender: "pdm-devel" On Thu Dec 4, 2025 at 1:51 PM CET, Christoph Heiss wrote: > This series adds integration with our automated installer [0] for all our > products. With this, Proxmox Datacenter Manager can be used for serving > answer files via HTTP(S) in an automated fashion. > > It provides two new panels: > > - Automated Installations: List all past and currently ongoing > installations. > - Prepared Answers: Enables users to do the whole CRUD cycle for > prepared answers, i.e. create new answers (from scratch or based on > existing ones), edit and delete. > > Permission-wise, everything is currently scoped on > /system/auto-installation. > > UI > == > > Happy about feedback regarding the UI, especially the editing dialog! By > the nature of it, the auto-installer has a lot more options than the > standard GUI/TUI installer, and it's kind of hard to not fully cramp up > the UI while still providing all options. > > TOML API > ======== > > The auto-installer (currently) only supports TOML as input format for > the answer, so we need to hack around a bit to serve TOML in the API. > This is done in patch #12, by implementing the api method > directly. > > Serving TOML from an endpoint under /api2/json/ obviously is rather > wrong, so I'm definitely open for suggestions. > We probably also don't want to implement `/api2/toml/` if I'd have to > guess (or would that be possible selectively, i.e. just for this one > endpoint?). > > Adding JSON support to proxmox-fetch-answer is on my list, but this > would still be needed if we want to keep compatibility with older ISOs. > Cool stuff, I didn't even know that somebody was working on this! Couldn't really try it out, I think there is some issue in the patches that you've posted. I'm getting a 'unresolved import `proxmox_installer_types::answer::fetch::AnswerFetchResponse' error when trying to compile PDM. Checking the code in the installer-types crate, I also couldn't find a type like this - could you cross-check? Thanks! _______________________________________________ pdm-devel mailing list pdm-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel