public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied-series: [PATCH access-control/manager/docs 0/9] close #2809: replication: add dedicated VM.Replicate privilege
Date: Wed, 30 Jul 2025 15:33:26 +0200	[thread overview]
Message-ID: <1753882366.mo0v27s9vv.astroid@yuna.none> (raw)
In-Reply-To: <20250718093024.55570-1-f.ebner@proxmox.com>

including a version bump for pve-access-control + versioned dependency
from pve-manager, and a tiny follow-up adding the new priv to the readme
as well ;)

On July 18, 2025 11:30 am, Fiona Ebner wrote:
> Currently, guest replication is guarded with Datastore.Allocate on
> '/storage', which is rather surprising. One could require
> Datastore.AllocateSpace on all involved storages, but having a
> dedicated privilege like for other VM operations like migration and
> snapshot seems to be more natural.
> 
> Manager patches 2/9 to 7/9 can be applied independently.
> 
> New manager depends on new access-control.
> 
> access-control:
> 
> Fiona Ebner (1):
>   add VM.Replicate privilege
> 
>  src/PVE/AccessControl.pm | 1 +
>  src/test/perm-test1.pl   | 8 ++++----
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> 
> manager:
> 
> Fiona Ebner (7):
>   api: replication: code style: order module imports
>   api: replication: add missing module imports
>   api: replication config: code style: order module imports
>   api: replication config: add missing module imports
>   api: replication config: remove dead code
>   api: replication: fix usages of RPCEnvironment check method
>   close #2809: api: replication: use VM.Replicate privilege
> 
>  PVE/API2/Replication.pm       | 38 ++++++++++++++++++-------------
>  PVE/API2/ReplicationConfig.pm | 42 ++++++++++++++++++++++++++---------
>  2 files changed, 54 insertions(+), 26 deletions(-)
> 
> 
> docs:
> 
> Fiona Ebner (1):
>   user management: privileges: document VM.Replicate privilege
> 
>  pveum.adoc | 1 +
>  1 file changed, 1 insertion(+)
> 
> 
> Summary over all repositories:
>   5 files changed, 60 insertions(+), 30 deletions(-)
> 
> -- 
> Generated by git-murpp 0.5.0
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 
> 


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


      parent reply	other threads:[~2025-07-30 13:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  9:30 [pve-devel] " Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH access-control 1/9] add " Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH manager 2/9] api: replication: code style: order module imports Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH manager 3/9] api: replication: add missing " Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH manager 4/9] api: replication config: code style: order " Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH manager 5/9] api: replication config: add missing " Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH manager 6/9] api: replication config: remove dead code Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH manager 7/9] api: replication: fix usages of RPCEnvironment check method Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH manager 8/9] close #2809: api: replication: use VM.Replicate privilege Fiona Ebner
2025-07-18  9:30 ` [pve-devel] [PATCH docs 9/9] user management: privileges: document " Fiona Ebner
2025-07-30 13:33 ` Fabian Grünbichler [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=1753882366.mo0v27s9vv.astroid@yuna.none \
    --to=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 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