* [pve-devel] [PATCH docs] pveum: remove misleading 'additionally' in perm-modify description
@ 2023-02-08 16:02 Lukas Wagner
2023-02-09 16:23 ` [pve-devel] applied: " Thomas Lamprecht
0 siblings, 1 reply; 2+ messages in thread
From: Lukas Wagner @ 2023-02-08 16:02 UTC (permalink / raw)
To: pve-devel
'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@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.
--
2.30.2
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-02-09 16:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-08 16:02 [pve-devel] [PATCH docs] pveum: remove misleading 'additionally' in perm-modify description Lukas Wagner
2023-02-09 16:23 ` [pve-devel] applied: " Thomas Lamprecht
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox