public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH installer] post-hook: save post hook data to /run/proxmox-installer
Date: Fri, 19 Dec 2025 15:06:24 +0100	[thread overview]
Message-ID: <20251219140654.918419-1-c.heiss@proxmox.com> (raw)

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 <c.heiss@proxmox.com>
---
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


                 reply	other threads:[~2025-12-19 14:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251219140654.918419-1-c.heiss@proxmox.com \
    --to=c.heiss@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal