From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] pveum: remove misleading 'additionally' in perm-modify description
Date: Wed, 8 Feb 2023 17:02:50 +0100 [thread overview]
Message-ID: <20230208160250.651769-1-l.wagner@proxmox.com> (raw)
'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
next reply other threads:[~2023-02-08 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 16:02 Lukas Wagner [this message]
2023-02-09 16:23 ` [pve-devel] applied: " 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=20230208160250.651769-1-l.wagner@proxmox.com \
--to=l.wagner@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