From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied-series: [PATCH-SERIES v2 manager/access-conrol/docs] fix #3402: add Pool.Audit permission
Date: Tue, 01 Jun 2021 11:06:28 +0200 [thread overview]
Message-ID: <1622538346.9e1m00h9qz.astroid@nora.none> (raw)
In-Reply-To: <20210520100341.31811-1-l.stechauner@proxmox.com>
On May 20, 2021 12:03 pm, Lorenz Stechauner wrote:
> Note: compat breaking changes for Pool.Allocate permission
>
> changes to v1:
> * docs patch now included
> * `/cluster/resources` now returns pool infomation for guests only if
> the requesting user has the Pool.Audit permission on the pool
>
>
>
> pve-manager:
>
> Lorenz Stechauner (1):
> fix #3402: add Pool.Audit permission
>
> PVE/API2/Cluster.pm | 7 ++++++-
> PVE/API2/Pool.pm | 7 ++++---
> PVE/API2/VZDump.pm | 2 +-
> 3 files changed, 11 insertions(+), 5 deletions(-)
>
>
> pve-access-control:
>
> Lorenz Stechauner (1):
> fix #3402: add Pool.Audit permission
>
> README | 1 +
> src/PVE/AccessControl.pm | 8 ++++++--
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
>
> pve-docs:
>
> Lorenz Stechauner (1):
> fix #3202: pveum: add Pool.Audit permission
>
> pveum.adoc | 1 +
> 1 file changed, 1 insertion(+)
> --
> 2.20.1
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
>
prev parent reply other threads:[~2021-06-01 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 10:03 [pve-devel] " Lorenz Stechauner
2021-05-20 10:03 ` [pve-devel] [PATCH v2 access-control 1/1] " Lorenz Stechauner
2021-05-20 10:03 ` [pve-devel] [PATCH v2 manager " Lorenz Stechauner
2021-05-20 10:03 ` [pve-devel] [PATCH v2 docs 1/1] fix #3202: pveum: " Lorenz Stechauner
2021-06-01 9:06 ` 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=1622538346.9e1m00h9qz.astroid@nora.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