From: alexandre derumier <aderumier@odiso.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager 2/2] api2 : network: anybridge: don't display bridges if user have access to vnets.
Date: Tue, 24 Aug 2021 08:12:12 +0200 [thread overview]
Message-ID: <715f0884db3d83b29a71c90bb34609d8b14b9b71.camel@odiso.com> (raw)
In-Reply-To: <a41b68b2-a2c9-0917-050b-7ae270c985d4@proxmox.com>
Le lundi 23 août 2021 à 18:39 +0200, Thomas Lamprecht a écrit :
> I mean, we could also just see bridges as a vnet and handle them with
> the
> `/sdn/vnets/<id>` path? Checking for every bridge/vnet if some priv.
> is
> available, we probably would need two privileges, one for "allowed to
> use"
> and a "allowed to modify" priv.
yes, I was thinking about this way too.
I'll rework this patch, thanks for the review.
prev parent reply other threads:[~2021-08-24 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 14:58 [pve-devel] [PATCH pve-manager 0/2] sdn: permissions improvments Alexandre Derumier
2021-08-05 14:58 ` [pve-devel] [PATCH pve-manager 1/1] api2 : network: anybridge: don't display bridges if user have access to vnets Alexandre Derumier
2021-08-05 14:58 ` [pve-devel] [PATCH pve-manager 1/2] permpathstore: add sdn zones Alexandre Derumier
2021-08-24 9:06 ` Thomas Lamprecht
2021-08-05 14:59 ` [pve-devel] [PATCH pve-manager 2/2] api2 : network: anybridge: don't display bridges if user have access to vnets Alexandre Derumier
2021-08-07 16:00 ` alexandre derumier
2021-08-23 16:39 ` Thomas Lamprecht
2021-08-24 6:12 ` alexandre derumier [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=715f0884db3d83b29a71c90bb34609d8b14b9b71.camel@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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