[pve-devel] [PATCH docs] pveum: remove misleading 'additionally' in perm-modify description

Lukas Wagner l.wagner at proxmox.com
Wed Feb 8 17:02:50 CET 2023

'additionally' in this context is a bit misleading, as it suggests
that e.g. 'VM.Allocate' AND 'Permissions.Modify' are needed, conflicting
with the previous paragraph.

Signed-off-by: Lukas Wagner <l.wagner at proxmox.com>
The ambiguity popped up in a recent support ticket.

 pveum.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pveum.adoc b/pveum.adoc
index 65d874a..24e903d 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -895,9 +895,9 @@ The `path` is a templated parameter (see
 `Permissions.Modify` privilege or,
 depending on the path, the following privileges as a possible substitute:
-* `/storage/...`: additionally requires 'Datastore.Allocate`
-* `/vms/...`: additionally requires 'VM.Allocate`
-* `/pool/...`: additionally requires 'Pool.Allocate`
+* `/storage/...`: requires 'Datastore.Allocate`
+* `/vms/...`: requires 'VM.Allocate`
+* `/pool/...`: requires 'Pool.Allocate`
 If the path is empty, `Permission.Modify` on `/access` is required.

More information about the pve-devel mailing list