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 4A3AB1FF0AB for ; Wed, 09 Sep 2026 13:12:46 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 3E86621634; Wed, 09 Sep 2026 13:12:39 +0200 (CEST) From: Erik Fastermann To: pbs-devel@lists.proxmox.com Subject: [PATCH proxmox-backup 3/5] report: include the s3 endpoint configuration Date: Wed, 9 Sep 2026 13:12:26 +0200 Message-ID: <20260909111228.217535-4-e.fastermann@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260909111228.217535-1-e.fastermann@proxmox.com> References: <20260909111228.217535-1-e.fastermann@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 1 AWL -0.468 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) KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 1.274 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: JXHFBU4KX6C67COSO447XLHJVNHBMNLW X-Message-ID-Hash: JXHFBU4KX6C67COSO447XLHJVNHBMNLW X-MailFrom: efastermann@ruth.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 CC: Erik Fastermann 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: s3.cfg is not included as a file, since it also holds the secret key of each endpoint. Listing the endpoints through the API keeps that distinction where it is already maintained, as the API returns the configuration without the secret. The access key is part of the returned configuration, matching what the API and the web interface expose to any user with Sys.Audit privileges. The JSON output format is used because the text table only covers a subset of the configured properties and because the report suppresses the table header. Signed-off-by: Erik Fastermann --- src/server/report.rs | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/server/report.rs b/src/server/report.rs index c22141810..b123c1fa9 100644 --- a/src/server/report.rs +++ b/src/server/report.rs @@ -46,6 +46,10 @@ fn project_commands() -> Vec { ), ("proxmox-backup-manager", vec!["ldap", "list"]), ("proxmox-backup-manager", vec!["openid", "list"]), + ( + "proxmox-backup-manager", + vec!["s3", "endpoint", "list", "--output-format", "json-pretty"], + ), ] } -- 2.47.3