[pbs-devel] [PATCH proxmox{, -backup} v3 0/4] s3: extend config by provider-quirks and client options by feature list

[Thomas Lamprecht]

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.