public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 manager 4/4] ui: qemu/HardwareView: fix CDRom permission checkss
Date: Fri, 19 Feb 2021 17:32:37 +0100	[thread overview]
Message-ID: <38976d6c-942e-b4e1-c70e-92c2fdef0211@proxmox.com> (raw)
In-Reply-To: <20210212155751.16045-5-a.lauterer@proxmox.com>

On 12.02.21 16:57, Aaron Lauterer wrote:
> There are several types of drives that use the same config keys. Most
> notably CDRom and regular VM disks (EFI and cloudinit exist as well).
> 
> Since there is a dedicated permission for CDRom drives we need to check
> permissions in more detail, depending on what type of drive it actually
> is for things like the edit, remove and Add -> CDRom buttons.
> 
> The permission check in the row definition itself which only checked for
> 'VM.Config.Disk' permissions (never_delete) had to be removed and finer
> grained checks added for the individual buttons. This also meant a bit
> of reshuffling in the checks what kind of disk the current one is.
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> 
> v2: improved permission checks in the GUI to make sure that CDRom things
> will behave as expected and the other things are kept as is. Meaning all
> other disks (cloudinit, efi, used, unused) still need VM.Config.Disk
> permissions.
> 
> Tested by giving a user only VMAudit and Config.CDRom permissions in the
> one case, and all VM.Config.* permissions except CDRom.
> 
>  www/manager6/qemu/HardwareView.js | 24 ++++++++++++++++--------
>  1 file changed, 16 insertions(+), 8 deletions(-)
> 
>

applied, but prefixed with some further cleanups which result was merged
into this one, so maybe a re-check would be good.
much thanks!




  reply	other threads:[~2021-02-19 16:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 15:57 [pve-devel] [PATCH v2 manager 1/4] ui: qemu/HardwareView: eslint: enforce "max-len" rule Aaron Lauterer
2021-02-12 15:57 ` [pve-devel] [PATCH v2 manager 2/4] ui: qemu/HardwareView: eslint: enforce "no-useless-concat" rule Aaron Lauterer
2021-02-19 15:47   ` [pve-devel] applied: " Thomas Lamprecht
2021-02-12 15:57 ` [pve-devel] [PATCH v2 manager 3/4] ui: qemu/HardwareView: eslint: enforce "no-shadow" rule Aaron Lauterer
2021-02-19 15:47   ` [pve-devel] applied: " Thomas Lamprecht
2021-02-12 15:57 ` [pve-devel] [PATCH v2 qemu-server] API: update_vm_api: check for CDROM on disk delete Aaron Lauterer
2021-02-22 16:40   ` [pve-devel] applied: " Thomas Lamprecht
2021-02-12 15:57 ` [pve-devel] [PATCH v2 manager 4/4] ui: qemu/HardwareView: fix CDRom permission checkss Aaron Lauterer
2021-02-19 16:32   ` Thomas Lamprecht [this message]
2021-02-19 15:46 ` [pve-devel] applied: [PATCH v2 manager 1/4] ui: qemu/HardwareView: eslint: enforce "max-len" rule 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=38976d6c-942e-b4e1-c70e-92c2fdef0211@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=a.lauterer@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal