From: Thomas Lamprecht <t.lamprecht@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 0/4] s3: extend config by provider-quirks and client options by feature list
Date: Mon, 4 Aug 2025 22:17:33 +0200 [thread overview]
Message-ID: <3e5e341f-3bf7-4103-89b2-b63db6a91a75@proxmox.com> (raw)
In-Reply-To: <20250804065331.45272-1-c.ebner@proxmox.com>
Am 04.08.25 um 08:54 schrieb Christian Ebner:
> These patches extend the s3 client configuration by the additional
> `provider-quirks` enum, allowing to switch to provider specific implementation
> details. The provider specific quirks are then mapped to a list of features and
> limitations, added to the s3 client options.
>
> 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.
Why not expose the actual quirk (features) directly? Even if we'd like to
have specific providers a user can select, that part could be a frontend
only feature, and tbh. for starters I'd even skip that, maybe documenting
provider to quirks in the PBS wiki might be a good option for now.
I'm just a bit wary of locking our backend in to those provider, as there
are quite a few of S3 provider, and not all might be here with us forever,
and having dozens of providers all mapping just to one or two actual
quirks each seems a bit overkill to me.
Sorry, I should have taken a closer check earlier to provider quicker
feedback.
_______________________________________________
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-08-04 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 6:53 Christian Ebner
2025-08-04 6:53 ` [pbs-devel] [PATCH proxmox v3 1/2] s3 client: api types: extend client config by optional provider quirks Christian Ebner
2025-08-04 6:53 ` [pbs-devel] [PATCH proxmox v3 2/2] s3 client: extend client options by feature list Christian Ebner
2025-08-04 6:53 ` [pbs-devel] [PATCH proxmox-backup v3 1/2] api: s3 config: allow to update or delete endpoint quirks Christian Ebner
2025-08-04 6:53 ` [pbs-devel] [PATCH proxmox-backup v3 2/2] ui: s3 endpoint: add provider specific quirk selector Christian Ebner
2025-08-04 20:17 ` Thomas Lamprecht [this message]
2025-08-05 5:58 ` [pbs-devel] [PATCH proxmox{, -backup} v3 0/4] s3: extend config by provider-quirks and client options by feature list Christian Ebner
2025-08-05 6:15 ` Thomas Lamprecht
2025-08-05 10:52 ` [pbs-devel] superseded: " 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=3e5e341f-3bf7-4103-89b2-b63db6a91a75@proxmox.com \
--to=t.lamprecht@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