From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PATCH proxmox{, -backup} 0/4] s3: extend config by quirks, implement backblaze B2 specific quirk
Date: Tue, 29 Jul 2025 08:36:35 +0200 [thread overview]
Message-ID: <82efcc97-482e-4df2-b2fc-7b9ad619f416@proxmox.com> (raw)
In-Reply-To: <20250728100154.556438-1-c.ebner@proxmox.com>
Please disregard this patches, I will send a v2 which incorporates
another provider which does not support the If-None-Match header as
reported in the community forum [0]. Further, I plan to split this a bit
better, allowing to configure the provider quirks in the s3 endpoint
config on PBS, but translate this to a feature list on the s3 client
options. By that this should be more flexible, allowing to more easily
extend for new quirky provider implementations with the same feature
limitations.
[0] https://forum.proxmox.com/threads/168954/
_______________________________________________
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-29 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 10:01 Christian Ebner
2025-07-28 10:01 ` [pbs-devel] [PATCH proxmox 1/2] s3 client: api types: extend client config by optional quirks Christian Ebner
2025-07-28 10:01 ` [pbs-devel] [PATCH proxmox 2/2] s3 client: skip setting `If-None-Match` header for Backblaze B2 Christian Ebner
2025-07-28 10:01 ` [pbs-devel] [PATCH proxmox-backup 1/2] api: s3 config: allow to update or delete endpoint quirks Christian Ebner
2025-07-28 10:01 ` [pbs-devel] [PATCH proxmox-backup 2/2] ui: s3 endpoint: add provider specific quirk selector Christian Ebner
2025-07-29 6:36 ` Christian Ebner [this message]
2025-07-29 8:19 ` [pbs-devel] superseded: [PATCH proxmox{, -backup} 0/4] s3: extend config by quirks, implement backblaze B2 specific quirk 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=82efcc97-482e-4df2-b2fc-7b9ad619f416@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