From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox{, -backup} v4 0/3] s3: extend endpoint config and client options by provider-quirks
Date: Tue, 5 Aug 2025 12:51:17 +0200 [thread overview]
Message-ID: <20250805105120.623089-1-c.ebner@proxmox.com> (raw)
These patches extend the s3 client configuration by an additional array
of `provider-quirks`, allowing to switch to provider specific implementation
details. The provider specific quirks are passed to the s3 client via it's
options on instantiation.
As first use-case, the `If-None-Match` header is not set during put object
requests to Backblaze B2 or Infomaniak object stores, as these fail with an
error with status code 501, therefore chunk uploads will fail.
The patches expose the provider quirks also in an dropdown list in the advanced
column of the s3 endpoint edit window.
Changes since v3:
- Use and expose quirks directly instead of mapping by provider list
Changes since v2:
- Rebased onto current master
Changes since v1:
- add Infomaniak as further provider not supporting the If-None-Match header
- introduce dedicate enum api type for both provider quirks and s3 client features
- add logic to map from provider to feature list
- skip If-None-Match header based on feature list, not provider
proxmox:
Christian Ebner (1):
s3 client: extend client config and options by optional provider
quirks
proxmox-s3-client/examples/s3_client.rs | 1 +
proxmox-s3-client/src/api_types.rs | 21 +++++++++++++++++++++
proxmox-s3-client/src/client.rs | 15 +++++++++++++--
3 files changed, 35 insertions(+), 2 deletions(-)
proxmox-backup:
Christian Ebner (2):
api: s3 config: allow to update or delete endpoint quirks
ui: s3 endpoint: add provider specific quirk selector
src/api2/config/s3.rs | 8 ++++++++
www/window/S3ClientEdit.js | 17 +++++++++++++++++
2 files changed, 25 insertions(+)
Summary over all repositories:
5 files changed, 60 insertions(+), 2 deletions(-)
--
Generated by git-murpp 0.8.1
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2025-08-05 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 10:51 Christian Ebner [this message]
2025-08-05 10:51 ` [pbs-devel] [PATCH proxmox v4 1/1] s3 client: extend client config and options by optional provider quirks Christian Ebner
2025-08-05 15:36 ` [pbs-devel] applied: " Thomas Lamprecht
2025-08-05 10:51 ` [pbs-devel] [PATCH proxmox-backup v4 1/2] api: s3 config: allow to update or delete endpoint quirks Christian Ebner
2025-08-05 15:40 ` [pbs-devel] applied: " Thomas Lamprecht
2025-08-05 10:51 ` [pbs-devel] [PATCH proxmox-backup v4 2/2] ui: s3 endpoint: add provider specific quirk selector Christian Ebner
2025-08-05 15:40 ` [pbs-devel] applied: " Thomas Lamprecht
2025-08-05 16:42 ` 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=20250805105120.623089-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