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 7417C1FF133 for ; Mon, 11 May 2026 17:19:41 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8E9001E282; Mon, 11 May 2026 17:19:40 +0200 (CEST) From: Christian Ebner To: pbs-devel@lists.proxmox.com Subject: [PATCH proxmox{,-backup} 0/3] add flag to opt-in using node proxy config for s3 connections Date: Mon, 11 May 2026 17:19:21 +0200 Message-ID: <20260511151924.901315-1-c.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 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: 1778512662654 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.070 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [datastore.rs,proxmox.com,s3.rs] Message-ID-Hash: 3I7JN4ZP27ND2JXGPOEAQZRJPCPFBM3H X-Message-ID-Hash: 3I7JN4ZP27ND2JXGPOEAQZRJPCPFBM3H X-MailFrom: c.ebner@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: Currently, if set the node proxy config is used unconditionally also for S3 client API connections. Since this is however not always the intention, allow users to expliciteley opt-in for individual S3 endpoint configurations. Reported in the community forum: https://forum.proxmox.com/threads/183436/ proxmox: Christian Ebner (1): s3-client: add flag to opt-in for using node proxy for connections proxmox-s3-client/src/api_types.rs | 8 ++++++++ 1 file changed, 8 insertions(+) proxmox-backup: Christian Ebner (2): api: config: allow editing the use-node-config flag for s3 endpoints ui: add opt-in flag for using the node proxy config for s3 connections pbs-datastore/src/datastore.rs | 14 ++++++++++++-- src/api2/admin/s3.rs | 8 +++++++- src/api2/config/s3.rs | 16 +++++++++++++++- www/window/S3ClientEdit.js | 13 +++++++++++++ 4 files changed, 47 insertions(+), 4 deletions(-) Summary over all repositories: 5 files changed, 55 insertions(+), 4 deletions(-) -- Generated by murpp 0.11.0