From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES manager] improve bulk action permissions
Date: Wed, 1 Mar 2023 15:22:18 +0100 [thread overview]
Message-ID: <20230301142220.130986-1-f.ebner@proxmox.com> (raw)
In the UI, fix the checks to use the same permission as the backend,
i.e. VM.PowerMgmt rather than Sys.PowerMgmt.
In the backend, also allow the bulk action when the user has the
appropriate permission for each guest in the passed-in list.
Fiona Ebner (2):
ui: bulk start/stop: align capability checks with backend
api: node: bulk actions: allow when user has permission for each guest
PVE/API2/Nodes.pm | 39 +++++++++++++++++++++++++++++++++---
www/manager6/node/CmdMenu.js | 4 +++-
www/manager6/node/Config.js | 6 +++---
3 files changed, 42 insertions(+), 7 deletions(-)
--
2.30.2
next reply other threads:[~2023-03-01 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 14:22 Fiona Ebner [this message]
2023-03-01 14:22 ` [pve-devel] [PATCH manager 1/2] ui: bulk start/stop: align capability checks with backend Fiona Ebner
2023-03-01 14:22 ` [pve-devel] [PATCH manager 2/2] api: node: bulk actions: allow when user has permission for each guest Fiona Ebner
2023-03-15 17:22 ` [pve-devel] applied-series: [PATCH-SERIES manager] improve bulk action permissions Thomas Lamprecht
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=20230301142220.130986-1-f.ebner@proxmox.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox