all lists on 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>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager/qemu-server 0/3] Cloudinit priv adaptations
Date: Wed, 7 Jun 2023 18:24:48 +0200	[thread overview]
Message-ID: <fdd01d52-881c-f976-e89e-1a8b7b49571c@proxmox.com> (raw)
In-Reply-To: <20230503075203.3293562-1-f.gruenbichler@proxmox.com>

Am 03/05/2023 um 09:52 schrieb Fabian Grünbichler:
> these patches adapt the Cloudinit privileges in the backend and GUI so
> that just giving out "VM.Config.Cloudinit" (and, if forceful
> regeneration outside of guest starts is desired, "VM.Config.CDROM") is
> enough to allow an unprivileged user to manage cloudinit for a given
> guest.
> 
> pve-managar
> 
> Fabian Grünbichler (2):
>   ui: cloudinit: match backend privilege checks
>   ui: cloudinit: also allow ipconfig with VM.Config.Cloudinit
> 
>  www/manager6/qemu/CloudInit.js | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> qemu-server
> 
> Fabian Grünbichler (1):
>   update_vm: allow setting ipconfigX with VM.Config.Cloudinit
> 
>  PVE/API2/Qemu.pm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 


applied series, with manager RFC 2/2 squashed into 1/2, thanks!




      parent reply	other threads:[~2023-06-07 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  7:52 [pve-devel] " Fabian Grünbichler
2023-05-03  7:52 ` [pve-devel] [PATCH manager 1/2] ui: cloudinit: match backend privilege checks Fabian Grünbichler
2023-05-03  7:52 ` [pve-devel] [RFC manager 2/2] ui: cloudinit: also allow ipconfig with VM.Config.Cloudinit Fabian Grünbichler
2023-05-03  7:52 ` [pve-devel] [RFC qemu-server 1/1] allow setting ipconfigX " Fabian Grünbichler
2023-06-07 16:24 ` 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=fdd01d52-881c-f976-e89e-1a8b7b49571c@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.gruenbichler@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal