From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Datacenter Manager development discussion
<pdm-devel@lists.proxmox.com>,
Shannon Sterz <s.sterz@proxmox.com>
Subject: [pdm-devel] applied-series: [PATCH datacenter-manager/proxmox/yew-comp v3 00/11] ACL edit api and ui components
Date: Thu, 28 Aug 2025 23:15:05 +0200 [thread overview]
Message-ID: <a8055f85-1d47-415d-b323-156a571f809e@proxmox.com> (raw)
In-Reply-To: <20250828105912.294887-1-s.sterz@proxmox.com>
On 28/08/2025 12:59, Shannon Sterz wrote:
> this series aims to make more parts of our access control list
> implementation re-usable between products. in a first step most of the
> relevant api endpoints and api types are moved to
> `proxmox-access-control`. this is done by adding a new `api` feature
> that includes the necessary api endpoints. the `AccessControlConfig`
> trait is also expanded to make the api endpoints more adaptable to
> different products. by providing default implementations for the newly
> added trait functions existing users don't need to change anything. it
> also tries to make the code here easier to understand as the checks
> could be hard to grasp previously.
>
> next the series adds components to proxmox-yew-comp to provide a panel
> for inspecting the current acl and adding or removing entries. this is
> done by using the existing `RoleSelector` and `AuthidSelector`
> components. the later is also slightly adapted to make it possible to
> change the api endpoint that roles are fetched from as well as the
> default role. the `AclView` component allows users of the crate to add
> more options for adding ACL entries. meaning they can configure distinct
> components for adding user, token or group permissions. this is done in
> a generic fashion so that extending this menu does not require changing
> the component again.
>
> finally proxmox-datacenter-manager is adapted to use the new api
> endpoints in `proxmox-access-control` and a permissions panel is
> implemented. note that this would benefit from some clean-up once
> permission path and such are cleaned up.
>
applied series, thanks!
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
prev parent reply other threads:[~2025-08-28 21:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 10:59 [pdm-devel] " Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH proxmox v3 1/6] access-control: add more types to prepare for api feature Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH proxmox v3 2/6] access-control: add acl " Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH proxmox v3 3/6] access-control: add comments to roles function of AccessControlConfig Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH proxmox v3 4/6] access-control: add generic roles endpoint to `api` feature Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH proxmox v3 5/6] access-control: api: refactor validation checks to re-use existing code Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH proxmox v3 6/6] access-control: api: refactor extract_acl_node_data to be non-recursive Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH yew-comp v3 1/3] api-types/role_selector: depend on common `RoleInfo` type Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH yew-comp v3 2/3] acl: add a view and semi-generic `EditWindow` for acl entries Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH yew-comp v3 3/3] role_selector/acl_edit: make api endpoint and default role configurable Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH datacenter-manager v3 1/2] server: use proxmox-access-control api implementations Shannon Sterz
2025-08-28 10:59 ` [pdm-devel] [PATCH datacenter-manager v3 2/2] ui: configuration: add panel for viewing and editing acl entries Shannon Sterz
2025-08-28 21:15 ` Thomas Lamprecht [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=a8055f85-1d47-415d-b323-156a571f809e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=s.sterz@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