From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Proxmox Datacenter Manager development discussion"
<pdm-devel@lists.proxmox.com>,
"Shannon Sterz" <s.sterz@proxmox.com>,
"Michael Köppl" <m.koeppl@proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager v3 08/11] api: subscription status: add support for view parameter
Date: Wed, 12 Nov 2025 11:26:48 +0100 [thread overview]
Message-ID: <DE6N7L9E8BCY.3QBZC0I75WRM4@proxmox.com> (raw)
In-Reply-To: <DE6KI4WUIMAR.2DUTABQTMK4U1@proxmox.com>
On Wed Nov 12, 2025 at 9:19 AM CET, Shannon Sterz wrote:
> On Tue Nov 11, 2025 at 3:46 PM CET, Michael Köppl wrote:
>> 1 comment inline
>>
>> On Thu Nov 6, 2025 at 2:43 PM CET, Lukas Wagner wrote:
>>> A view allows one to get filtered subset of all resources, based on
>>> filter rules defined in a config file. Views integrate with the
>>> permission system - if a user has permissions on /view/{view-id}, then
>>> these privileges are transitively applied to all resources which are
>>> matched by the rules. All other permission checks are replaced if
>>> requesting data through a view.
>>>
>>> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
>>> ---
>>>
>>> Notes:
>>> Changes since v2:
>>> - make sure to not filter out a remote if it has been explicitly
>>> included
>>>
>>> server/src/api/resources.rs | 66 ++++++++++++++++++++++++++++++-------
>>> 1 file changed, 54 insertions(+), 12 deletions(-)
>>>
>>> diff --git a/server/src/api/resources.rs b/server/src/api/resources.rs
>>> index 143335fe..2930da8b 100644
>>> --- a/server/src/api/resources.rs
>>> +++ b/server/src/api/resources.rs
>>> @@ -552,6 +552,10 @@ pub async fn get_status(
>>> default: false,
>>> description: "If true, includes subscription information per node (with enough privileges)",
>>> },
>>> + view: {
>>> + schema: VIEW_ID_SCHEMA,
>>> + optional: true,
>>> + },
>>> },
>>> },
>>> returns: {
>>> @@ -566,6 +570,7 @@ pub async fn get_status(
>>> pub async fn get_subscription_status(
>>> max_age: u64,
>>> verbose: bool,
>>> + view: Option<String>,
>>> rpcenv: &mut dyn RpcEnvironment,
>>> ) -> Result<Vec<RemoteSubscriptions>, Error> {
>>> let (remotes_config, _) = pdm_config::remotes::config()?;
>>> @@ -574,9 +579,17 @@ pub async fn get_subscription_status(
>>>
>>> let auth_id = rpcenv.get_auth_id().unwrap().parse()?;
>>> let user_info = CachedUserInfo::new()?;
>>> - let allow_all = user_info
>>> - .check_privs(&auth_id, &["resource"], PRIV_RESOURCE_AUDIT, false)
>>> - .is_ok();
>>> +
>>> + let allow_all = if let Some(view) = &view {
>>> + user_info.check_privs(&auth_id, &["view", view], PRIV_RESOURCE_AUDIT, false)?;
>>> + false
>>> + } else {
>>> + user_info
>>> + .check_privs(&auth_id, &["resource"], PRIV_RESOURCE_AUDIT, false)
>>> + .is_ok()
>>> + };
>>> +
>>> + let view = views::get_optional_view(view.as_deref())?;
>>>
>>> let check_priv = |remote_name: &str| -> bool {
>>> user_info
>>> @@ -590,35 +603,64 @@ pub async fn get_subscription_status(
>>> };
>>>
>>> for (remote_name, remote) in remotes_config {
>>> - if !allow_all && !check_priv(&remote_name) {
>>> + if let Some(view) = &view {
>>> + if view.can_skip_remote(&remote_name) {
>>> + continue;
>>> + }
>>> + } else if !allow_all && !check_priv(&remote_name) {
>>> continue;
>>> }
>>>
>>> + let view = view.clone();
>>> +
>>> let future = async move {
>>> let (node_status, error) =
>>> match get_subscription_info_for_remote(&remote, max_age).await {
>>> - Ok(node_status) => (Some(node_status), None),
>>> + Ok(mut node_status) => {
>>> + node_status.retain(|node, _| {
>>> + if let Some(view) = &view {
>>> + view.is_node_included(&remote.id, node)
>>> + } else {
>>> + true
>>> + }
>>> + });
>>> + (Some(node_status), None)
>>> + }
>>> Err(error) => (None, Some(error.to_string())),
>>> };
>>>
>>> - let mut state = RemoteSubscriptionState::Unknown;
>>> + let state = if let Some(node_status) = &node_status {
>>> + if let Some(view) = view {
>>> + if error.is_some() && !view.is_remote_explicitly_included(&remote.id) {
>>
>> Can this ever be be true? From the code above, you can never have the
>> case that node_status and error are both Some(...) at the same time, so
>> error.is_some() would always evaluate to false here, unless I'm missing
>> something.
>>
>> I think you'd have to put the check outside of this block.
>>
>> if let Some(view) = &view {
>> if error.is_some() && !view.is_remote_explicitly_included(&remote.id) {
>> return None;
>> }
>> }
>>
>> let state = if let Some(node_status) = &node_status {
>> ...
>> }
>>
>
> i thikn this is right, at least i noted something similar in a previous
> version of this patch series already. thanks for spotting it again!
>
> https://lore.proxmox.com/all/DDVMQ0KGW0IP.50W15XZS8TQ@proxmox.com/
>
Ah, my bad. I remember reading your comment about this patch, but I
think it was overshadowed by some other changes, including the
`is_remote_explicitly_included` thing.
I moved the block as suggested.
Thanks :)
>>> + // Don't leak the existence of failed remotes unless they were explicitly
>>> + // pulled in by a `include remote:<id>` rule.
>>> + return None;
>>> + }
>>> + }
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-11-12 10:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 13:43 [pdm-devel] [PATCH datacenter-manager v3 00/11] backend implementation for view filters Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 01/11] pdm-api-types: views: add ViewConfig type Lukas Wagner
2025-11-11 10:57 ` Michael Köppl
2025-11-12 10:04 ` Lukas Wagner
2025-11-11 10:58 ` Michael Köppl
2025-11-12 10:05 ` Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 02/11] pdm-config: views: add support for views Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 03/11] acl: add '/view' and '/view/{view-id}' as allowed ACL paths Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 04/11] views: add implementation for view resource filtering Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 05/11] api: resources: list: add support for view parameter Lukas Wagner
2025-11-11 14:31 ` Michael Köppl
2025-11-12 10:14 ` Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 06/11] api: resources: top entities: " Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 07/11] api: resources: status: " Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 08/11] api: subscription " Lukas Wagner
2025-11-11 14:46 ` Michael Köppl
2025-11-12 8:19 ` Shannon Sterz
2025-11-12 10:26 ` Lukas Wagner [this message]
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 09/11] api: remote-tasks: " Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 10/11] pdm-client: resource list: add view-filter parameter Lukas Wagner
2025-11-06 13:43 ` [pdm-devel] [PATCH datacenter-manager v3 11/11] pdm-client: top entities: " Lukas Wagner
2025-11-11 15:00 ` [pdm-devel] [PATCH datacenter-manager v3 00/11] backend implementation for view filters Michael Köppl
2025-11-12 10:37 ` [pdm-devel] superseded: " Lukas Wagner
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=DE6N7L9E8BCY.3QBZC0I75WRM4@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=m.koeppl@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