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 B59AD1FF135 for ; Sun, 05 Apr 2026 10:39:25 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 39596188CF; Sun, 5 Apr 2026 10:39:58 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Christian Ebner Subject: applied: [PATCH proxmox-backup] pbs-config: refactor and move helper to detect config digest changes Date: Sun, 5 Apr 2026 10:39:49 +0200 Message-ID: <177537835555.2576509.17240572929953881239.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260402134110.848575-1-c.ebner@proxmox.com> References: <20260402134110.848575-1-c.ebner@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: 1775378332240 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.002 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: QA6R5H6LMPNIET54F6MWEX6MYJ54LJXH X-Message-ID-Hash: QA6R5H6LMPNIET54F6MWEX6MYJ54LJXH 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 Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Thu, 02 Apr 2026 15:41:10 +0200, Christian Ebner wrote: > This is such a common pattern for a huge number of API handlers that > refactoring it into a common helper is waranted. As a positive side > effect, direct dependencies on the hex crate for the API handlers are > reduced. > > By moving the helper to pbs-config it can be used also from within > pbs-config, which will be used to detect config changes for encrypton > keys in the future. > > [...] Applied, two general comments replied as seprate mail, thanks! [1/1] pbs-config: refactor and move helper to detect config digest changes commit: 1bab5905d496296bd0bb2640400cc3e91f266531