From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Proxmox Backup Server development discussion"
<pbs-devel@lists.proxmox.com>,
"Christian Ebner" <c.ebner@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox{, -backup} v3 00/10] s3: implement list buckets and use bucket selector for datastore creation
Date: Thu, 31 Jul 2025 13:55:24 +0200 [thread overview]
Message-ID: <DBQ7YRTZE0NV.LM0ZMFK4WZR1@proxmox.com> (raw)
In-Reply-To: <20250731104814.99768-1-c.ebner@proxmox.com>
On Thu Jul 31, 2025 at 12:48 PM CEST, Christian Ebner wrote:
> This patches aim to increase usability for the user by allowing to list
> accessible buckets during datastore creation.
>
> For this, the proxmox s3 client is extended by the list buckets method, fetching
> accessible buckets from the s3 api. This requires the client instantiation to be
> possible without the bucket name, making it therefore optional. Further, the
> regex for the config endpoint url must be restricted to have the bucket name
> template pattern always at the start of the template. With these changes, it is
> then possible to fetch the buckets given the required permissions to do so.
>
> On the proxmox backup server side, the api endpoints to fetch the bucket list
> are implemented as well as the corresponding cli command. Finally, the bucket
> name field in the datastore edit window is replaced by an s3 bucket selector,
> which loads the accessible bucket names via the api.
>
Works fine now, also when there are multiple buckets. Nice work!
Tested-by: Lukas Wagner <l.wagner@proxmox.com>
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-07-31 11:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 10:48 Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox v3 1/4] s3 client: restrict bucket template pattern to start of endpoint url Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox v3 2/4] s3 client: make bucket name optional in S3 client options Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox v3 3/4] s3 client: implement list buckets method Christian Ebner
2025-07-31 11:43 ` Lukas Wagner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox v3 4/4] s3 client: api types: add bucket list item type Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox-backup v3 1/6] ui: fix formatting issues using proxmox-biome Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox-backup v3 2/6] datastore: wrap bucket name, as in is now optional in the s3 client Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox-backup v3 3/6] api: admin s3: make store prefix for check command optional Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox-backup v3 4/6] api: config s3: add bucket list api endpoint Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox-backup v3 5/6] bin: expose list buckets as proxmox-backup-manager s3 subcommand Christian Ebner
2025-07-31 10:48 ` [pbs-devel] [PATCH proxmox-backup v3 6/6] ui: replace bucket field by bucket selector Christian Ebner
2025-07-31 11:55 ` Lukas Wagner [this message]
2025-07-31 13:02 ` [pbs-devel] [PATCH proxmox{, -backup} v3 00/10] s3: implement list buckets and use bucket selector for datastore creation Christian Ebner
2025-07-31 13:17 ` Thomas Lamprecht
2025-07-31 13:28 ` Thomas Lamprecht
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=DBQ7YRTZE0NV.LM0ZMFK4WZR1@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=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