From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id CC4371FF0E5 for ; Wed, 29 Jul 2026 14:17:31 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 9E60A21375; Wed, 29 Jul 2026 14:17:31 +0200 (CEST) Date: Wed, 29 Jul 2026 14:17:03 +0200 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= Subject: applied-series: [PATCH proxmox{,-backup} 0/3] add flag to opt-in using node proxy config for s3 connections To: Christian Ebner , pbs-devel@lists.proxmox.com References: <20260511151924.901315-1-c.ebner@proxmox.com> In-Reply-To: <20260511151924.901315-1-c.ebner@proxmox.com> MIME-Version: 1.0 User-Agent: astroid/0.17.0 (https://github.com/astroidmail/astroid) Message-Id: <1785327416.40docp2dja.astroid@yuna.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1785327419775 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.132 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust 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: XU2GYDLW62AJ6JEYNLUNDJRLI65FJGS6 X-Message-ID-Hash: XU2GYDLW62AJ6JEYNLUNDJRLI65FJGS6 X-MailFrom: f.gruenbichler@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 May 11, 2026 5:19 pm, Christian Ebner wrote: > 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. >=20 > Reported in the community forum: > https://forum.proxmox.com/threads/183436/ >=20 >=20 > proxmox: >=20 > Christian Ebner (1): > s3-client: add flag to opt-in for using node proxy for connections >=20 > proxmox-s3-client/src/api_types.rs | 8 ++++++++ > 1 file changed, 8 insertions(+) >=20 >=20 > proxmox-backup: >=20 > 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 >=20 > 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(-) >=20 >=20 > Summary over all repositories: > 5 files changed, 55 insertions(+), 4 deletions(-) >=20 > --=20 > Generated by murpp 0.11.0 >=20 >=20 >=20 >=20 >=20