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 DFEF91FF137 for ; Tue, 31 Mar 2026 23:30:56 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B93927F6F; Tue, 31 Mar 2026 23:31:24 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Christian Ebner Subject: partially-applied: [PATCH proxmox{,-backup} v4 0/8] fix #6716: Add support for http proxy configuration for S3 endpoints Date: Tue, 31 Mar 2026 23:30:16 +0200 Message-ID: <177499260903.801440.16178603165380770825.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260327121319.628881-1-c.ebner@proxmox.com> References: <20260327121319.628881-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: 1774992595929 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.503 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 1 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 1 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 1 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 Message-ID-Hash: NS34GWUMPF5TKUGMLTQY7FL7NBLT4MD2 X-Message-ID-Hash: NS34GWUMPF5TKUGMLTQY7FL7NBLT4MD2 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 Fri, 27 Mar 2026 13:13:11 +0100, Christian Ebner wrote: > This patch series exposes the nodes proxy config setting to the S3 > clients for datastores backed by an S3 object store. > > To honor crate boundaries, the proxy configuration is refactored to > be part of pbs-config instead of proxmox-backup. The API types are > move to pbs-api-types, inlining proxmox_backup::tools::config::from_property_string() > and NodeConfig::validate() to do so without creating additional unwanted > dependencies. The schema definition for the proxy is moved to proxmox-http > instead, already containing the proxy config definition. > > [...] Applied the proxmox part, thanks! [1/2] http: move http proxy schema from PBS to crate's api types commit: d3823019f5165917e8076d41dde32d61092e34cf [2/2] pbs-api-types: move over NodeConfig and related api type from PBS commit: 1bcfae925eb426fbaa74b15c2f5c4c07828130e3