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 8C95D1FF187 for ; Fri, 19 Dec 2025 15:06:18 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4E6F1D8CB; Fri, 19 Dec 2025 15:07:06 +0100 (CET) From: Christoph Heiss To: pve-devel@lists.proxmox.com Date: Fri, 19 Dec 2025 15:06:24 +0100 Message-ID: <20251219140654.918419-1-c.heiss@proxmox.com> X-Mailer: git-send-email 2.51.2 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1766153209492 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.052 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 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [main.rs] Subject: [pve-devel] [PATCH installer] post-hook: save post hook data to /run/proxmox-installer X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Having the sent post-hook data available somewhere in the installatino environment after the fact is seful for easily inspecting a failed/rejected post-hook. Signed-off-by: Christoph Heiss --- It's a rather niche thing and more useful to developers than users. Added this while working on the PDM integration, and thought it might be nice to have this in general, especially since it does not have any other impact. proxmox-post-hook/src/main.rs | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/proxmox-post-hook/src/main.rs b/proxmox-post-hook/src/main.rs index 9989389..a1aee1c 100644 --- a/proxmox-post-hook/src/main.rs +++ b/proxmox-post-hook/src/main.rs @@ -662,6 +662,15 @@ fn do_main() -> Result<()> { let info = with_chroot(|target_path| PostHookInfo::gather(target_path, &answer))?; + if let Err(err) = fs::write( + "/run/proxmox-installer/post-hook-data.json", + serde_json::to_string_pretty(&info)?, + ) { + eprintln!( + "Failed to write post-installation-webhook data to /run/proxmox-installer: {err:#}" + ); + } + proxmox_installer_common::http::post( url, cert_fingerprint.as_deref(), -- 2.51.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel