public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: [pbs-devel] applied-series: [PATCH proxmox-backup v2 0/8] remove objects from s3 backend on datastore destroy
Date: Wed, 30 Jul 2025 16:51:30 +0200	[thread overview]
Message-ID: <175388708889.3678520.6190764868106234351.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250730075750.36014-1-c.ebner@proxmox.com>

On Wed, 30 Jul 2025 09:57:42 +0200, Christian Ebner wrote:
> This patch series makes sure the datastore contents are also removed
> from the s3 backend if the datastore is destroyed with the remove all
> data flag being set.
> 
> The first 6 patches fix clippy warnings and refactor the s3 client from
> datastore config generation into a dedicated helper, since the last
> patch requires that as well and this would be the third ocurence thereof.
> 
> [...]

Applied, thanks!

[1/8] tree wide: fix useless borrow warnings
      commit: 6b03212d683871a2fae9432b5c34418f9c1d5e4b
[2/8] client: backup writer: elide lifetime which can be auto inferred
      commit: 81b13b8dc0abfca2af73cb6a46ac554746bd71f9
[3/8] api: tape: fix clippy warning on map iteration
      commit: 4c074d863c86c217037fdb9eb3585c60636f9195
[4/8] datastore: fix clippy warning checking file extension
      commit: 7ed70f8fa2b7211475ef698c7c6f37296dca535a
[5/8] datastore: fix clippy warning to use ? on option
      commit: e5000d41d8330d1b9c61e86cadbee30bfcbce689
[6/8] datastore: add helper to get s3 client from datastore config
      commit: fc38e367e422dcce96348f0f786340c90484d1b5
[7/8] datastore: delete all objects on datastore destroy with remove data
      commit: ed276d7a6718eee8b0ac5acd1045885fb43310da
[8/8] ui: switch datastore destroy label text on backend type
      commit: 42388699e61e5af4c8cf1e21ea0d2e23ee1459ab


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


      parent reply	other threads:[~2025-07-30 14:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  7:57 [pbs-devel] " Christian Ebner
2025-07-30  7:57 ` [pbs-devel] [PATCH proxmox-backup v2 1/8] tree wide: fix useless borrow warnings Christian Ebner
2025-07-30  7:57 ` [pbs-devel] [PATCH proxmox-backup v2 2/8] client: backup writer: elide lifetime which can be auto inferred Christian Ebner
2025-07-30  7:57 ` [pbs-devel] [PATCH proxmox-backup v2 3/8] api: tape: fix clippy warning on map iteration Christian Ebner
2025-07-30  7:57 ` [pbs-devel] [PATCH proxmox-backup v2 4/8] datastore: fix clippy warning checking file extension Christian Ebner
2025-07-30  7:57 ` [pbs-devel] [PATCH proxmox-backup v2 5/8] datastore: fix clippy warning to use ? on option Christian Ebner
2025-07-30  7:57 ` [pbs-devel] [PATCH proxmox-backup v2 6/8] datastore: add helper to get s3 client from datastore config Christian Ebner
2025-07-30  7:57 ` [pbs-devel] [PATCH proxmox-backup v2 7/8] datastore: delete all objects on datastore destroy with remove data Christian Ebner
2025-07-30  7:57 ` [pbs-devel] [PATCH proxmox-backup v2 8/8] ui: switch datastore destroy label text on backend type Christian Ebner
2025-07-30 14:51 ` Thomas Lamprecht [this message]

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=175388708889.3678520.6190764868106234351.b4-ty@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal