From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 0/6] fix various s3 related ui/cli/doc issues
Date: Tue, 22 Jul 2025 14:48:31 +0200 [thread overview]
Message-ID: <20250722124837.864242-1-c.ebner@proxmox.com> (raw)
This patch series is a followup to the s3 object store backend for
Proxmox Backup Server patch series found at:
https://lore.proxmox.com/pbs-devel/20250722101106.526438-1-c.ebner@proxmox.com/T/
Most prominently, it moves the S3 endpoint configuration to the remotes,
splitting the remotes into tabs for the s3 configuration and the remote
Proxmox Backup Server configuration.
The other patches mostly touch naming, preferring `endpoint` over
`client` for s3 endpoint configurations.
Also, fixes a small ui issue found by Lukas during testing (thanks for
the report, still plan to refactor the whole datastore edit window as
promised once I find the time).
The last patch improves ui by allowing the user to pass the https scheme
prefix to the endpoint in the ui, stripping it for the backend config.
Christian Ebner (6):
ui: add tabs for remotes and move s3 endpoint config to it
ui: use S3 endpoint over S3 client for ui elements
cli: use `endpoint` over `client` for s3 endpoint subcommands
docs: use `endpoint` over `client` for the s3 endpoint configuration
ui: default for s3 overwrite-in-use to be disabled
ui: s3 client edit: allow for https scheme prefix in endpoint input
docs/storage.rst | 29 ++++++++-------
src/bin/proxmox_backup_manager/s3.rs | 14 +++----
www/Makefile | 1 +
www/NavigationTree.js | 8 +---
www/config/RemoteView.js | 2 +-
www/config/RemotesOverview.js | 55 ++++++++++++++++++++++++++++
www/config/S3ClientView.js | 2 +-
www/form/S3ClientSelector.js | 2 +-
www/window/DataStoreEdit.js | 6 ++-
www/window/S3ClientEdit.js | 6 ++-
10 files changed, 92 insertions(+), 33 deletions(-)
create mode 100644 www/config/RemotesOverview.js
--
2.47.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2025-07-22 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 12:48 Christian Ebner [this message]
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 1/6] ui: add tabs for remotes and move s3 endpoint config to it Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 2/6] ui: use S3 endpoint over S3 client for ui elements Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 3/6] cli: use `endpoint` over `client` for s3 endpoint subcommands Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 4/6] docs: use `endpoint` over `client` for the s3 endpoint configuration Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 5/6] ui: default for s3 overwrite-in-use to be disabled Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 6/6] ui: s3 client edit: allow for https scheme prefix in endpoint input Christian Ebner
2025-07-22 20:25 ` [pbs-devel] applied: [PATCH proxmox-backup 0/6] fix various s3 related ui/cli/doc issues Thomas Lamprecht
2025-07-23 6:33 ` Christian Ebner
2025-07-23 7:27 ` Thomas Lamprecht
2025-07-23 7:37 ` Christian Ebner
2025-07-23 7:55 ` Thomas Lamprecht
2025-07-23 10:04 ` Christian Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250722124837.864242-1-c.ebner@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox