From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH-SERIES storage v2 0/2] api: prune backups: improve permission checks
Date: Mon, 9 Nov 2026 01:07:53 +0100 [thread overview]
Message-ID: <179418286965.3956036.846392862396269187.b4-ty@b4> (raw)
In-Reply-To: <20261105103736.52417-1-f.ebner@proxmox.com>
On Thu, 05 Nov 2026 11:35:42 +0100, Fiona Ebner wrote:
> Changes in v2:
> * Different approach. Do not use check_volume_access() for filtering.
> Aligning the permissions between the dry run and active run is more
> natural here.
>
> Align the permission checks for dry run and active run, since that is
> natural here. And remove an unnatural restriction for the case where
> an explicit guest ID is specified.
>
> [...]
Applied, thanks!
[1/2] api: prune backups: align permission check for dry run and active run
https://git.proxmox.com/?p=pve-storage.git;a=commitdiff;h=7a7647768cd2cdcc473154c997be3b1603b36d25
[2/2] api: prune backups: allow Datastore.Allocate even without VM.Backup
https://git.proxmox.com/?p=pve-storage.git;a=commitdiff;h=34de45f4e0931cbc7dd5aa60882894a9a1b4d135
prev parent reply other threads:[~2026-11-09 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 10:35 [PATCH-SERIES storage v2 0/2] api: prune backups: improve permission checks Fiona Ebner
2026-11-05 10:35 ` [PATCH storage v2 1/2] api: prune backups: align permission check for dry run and active run Fiona Ebner
2026-11-05 10:35 ` [PATCH storage v2 2/2] api: prune backups: allow Datastore.Allocate even without VM.Backup Fiona Ebner
2026-11-09 0:07 ` 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=179418286965.3956036.846392862396269187.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.