public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Shannon Sterz" <s.sterz@proxmox.com>,
	"Lukas Wagner" <l.wagner@proxmox.com>
Cc: Proxmox Datacenter Manager development discussion
	<pdm-devel@lists.proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager v2 3/4] api: add /remotes/tasks/refresh
Date: Mon, 29 Dec 2025 15:57:48 +0100	[thread overview]
Message-ID: <DFASEOYG4Y4G.2AFDAOCT47GBQ@proxmox.com> (raw)
In-Reply-To: <DF28QXM9KN8W.S39VSZX64Y75@proxmox.com>

On Fri Dec 19, 2025 at 2:52 PM CET, Shannon Sterz wrote:
> some comments in-line:
>
> On Thu Dec 18, 2025 at 3:20 PM CET, Lukas Wagner wrote:
[...]
>>  #[api(
>> @@ -168,3 +175,80 @@ async fn task_statistics(
>>
>>      Ok(TaskStatistics { by_type, by_remote })
>>  }
>> +
>> +#[api(
>> +    input: {
>> +        properties: {
>> +            remote: {
>> +                schema: REMOTE_ID_SCHEMA,
>> +                optional: true,
>
> i wonder if it makes sense to allow a list of remotes here instead of
> just a single remote.

Yeah, good point. I don't see any reason why not, especially since the
refresh_taskcache function supports a list of remotes anyway.

As for permissions, I will implement it so that if `remotes` is
provided, the user requires the appropriate permissions for *all* off
them - opposed to just not showing them as we do for `remotes` is not
provided.

I will change this to a `remotes` parameter for v2.

Thanks a lot, Shannon!

>
> this api endpoint would also benefit from a short description on how
> this parameter influences the result imo.
>

Will do!

>> +            },
>> +        },
>> +    },
>> +    access: {
>> +        permission: &Permission::Anybody,
>> +        description: "Resource.Modify privileges are needed on /resource/{remote}",
>> +    },
>> +    returns: { type: UPID }
>> +)]
>> +/// Refresh the update summary of all remotes.
>> +pub fn refresh_remote_tasks(
>> +    remote: Option<String>,
>> +    rpcenv: &mut dyn RpcEnvironment,
>> +) -> Result<UPID, Error> {
>> +    let (config, _digest) = pdm_config::remotes::config()?;
>> +
>> +    let auth_id: Authid = rpcenv.get_auth_id().unwrap().parse()?;
>> +    let user_info = CachedUserInfo::new()?;

[...]


_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel


  reply	other threads:[~2025-12-29 14:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 14:20 [pdm-devel] [PATCH datacenter-manager/proxmox-yew-comp v2 0/6] manual refresh button for remote task cache Lukas Wagner
2025-12-18 14:20 ` [pdm-devel] [PATCH proxmox-yew-comp v2 1/2] task list: add support for starting refresh tasks Lukas Wagner
2025-12-18 14:20 ` [pdm-devel] [PATCH proxmox-yew-comp v2 2/2] loadable component: don't trigger reload when starting a task Lukas Wagner
2025-12-18 14:20 ` [pdm-devel] [PATCH datacenter-manager v2 1/4] remote tasks: move implementation to server crate Lukas Wagner
2025-12-19 13:50   ` Shannon Sterz
2025-12-29 14:54     ` Lukas Wagner
2025-12-18 14:20 ` [pdm-devel] [PATCH datacenter-manager v2 2/4] remote tasks: implement `refresh_task_cache` for manual task fetching Lukas Wagner
2025-12-18 14:20 ` [pdm-devel] [PATCH datacenter-manager v2 3/4] api: add /remotes/tasks/refresh Lukas Wagner
2025-12-19 13:52   ` Shannon Sterz
2025-12-29 14:57     ` Lukas Wagner [this message]
2025-12-18 14:20 ` [pdm-devel] [PATCH datacenter-manager v2 4/4] ui: remote task view: set refresh_task_url property for task viewer Lukas Wagner
2025-12-19 13:53 ` [pdm-devel] [PATCH datacenter-manager/proxmox-yew-comp v2 0/6] manual refresh button for remote task cache Shannon Sterz
2025-12-29 15:31 ` [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=DFASEOYG4Y4G.2AFDAOCT47GBQ@proxmox.com \
    --to=l.wagner@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal