all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Lukas Wagner <l.wagner@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH datacenter-manager 5/7] api: pve tasks: use shared helpers for RemoteUpid handling
Date: Wed, 12 Nov 2025 10:42:01 +0100	[thread overview]
Message-ID: <20251112094203.112452-6-l.wagner@proxmox.com> (raw)
In-Reply-To: <20251112094203.112452-1-l.wagner@proxmox.com>

The helpers defined in RemoteUpid, as well as the verify_upid helper
make the code much shorter and easy to read.

Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
 server/src/api/pve/tasks.rs | 62 ++++++++++---------------------------
 1 file changed, 17 insertions(+), 45 deletions(-)

diff --git a/server/src/api/pve/tasks.rs b/server/src/api/pve/tasks.rs
index e66712ac..5edce149 100644
--- a/server/src/api/pve/tasks.rs
+++ b/server/src/api/pve/tasks.rs
@@ -1,17 +1,16 @@
 //! Access to PVE tasks.
 
-use anyhow::{bail, format_err, Error};
+use anyhow::Error;
 
 use proxmox_router::{list_subdirs_api_method, Permission, Router, RpcEnvironment, SubdirMap};
 use proxmox_schema::api;
 use proxmox_sortable_macro::sortable;
 
-use pdm_api_types::remotes::REMOTE_ID_SCHEMA;
+use pdm_api_types::remotes::{RemoteType, REMOTE_ID_SCHEMA};
 use pdm_api_types::{
     RemoteUpid, NODE_SCHEMA, PRIV_RESOURCE_AUDIT, PRIV_RESOURCE_MANAGE,
     TASKLOG_DOWNLOAD_PARAM_SCHEMA, TASKLOG_LIMIT_PARAM_SCHEMA, TASKLOG_START_PARAM_SCHEMA,
 };
-use pve_api_types::PveUpid;
 
 use super::{connect, connect_to_remote, get_remote};
 
@@ -82,23 +81,14 @@ async fn list_tasks(
 async fn stop_task(remote: String, upid: RemoteUpid) -> Result<(), Error> {
     let (remotes, _) = pdm_config::remotes::config()?;
 
-    if upid.remote() != remote {
-        bail!(
-            "remote '{remote}' does not match remote in upid ('{}')",
-            upid.remote()
-        );
-    }
+    crate::api::verify_upid(&remote, RemoteType::Pve, &upid)?;
 
-    let pve = get_remote(&remotes, upid.remote())?;
+    let pve_upid = upid.pve_upid()?;
 
-    let pve_upid: PveUpid = upid
-        .upid()
-        .parse()
-        .map_err(|err| format_err!("invalid upid for PVE: {} - {err}", upid.upid()))?;
+    let remote = get_remote(&remotes, upid.remote())?;
+    let client = connect(remote)?;
 
-    let pve = connect(pve)?;
-
-    Ok(pve.stop_task(&pve_upid.node, upid.upid()).await?)
+    Ok(client.stop_task(&pve_upid.node, upid.upid()).await?)
 }
 
 #[api(
@@ -128,24 +118,15 @@ pub async fn get_task_status(
 ) -> Result<pve_api_types::TaskStatus, Error> {
     let (remotes, _) = pdm_config::remotes::config()?;
 
-    if upid.remote() != remote {
-        bail!(
-            "remote '{remote}' does not match remote in upid ('{}')",
-            upid.remote()
-        );
-    }
+    crate::api::verify_upid(&remote, RemoteType::Pve, &upid)?;
 
-    let pve = get_remote(&remotes, upid.remote())?;
+    let pve_upid = upid.pve_upid()?;
 
-    let pve_upid: PveUpid = upid
-        .upid()
-        .parse()
-        .map_err(|err| format_err!("invalid upid for PVE: {} - {err}", upid.upid()))?;
-
-    let pve = connect(pve)?;
+    let remote = get_remote(&remotes, upid.remote())?;
+    let client = connect(remote)?;
 
     loop {
-        let status = pve.get_task_status(&pve_upid.node, upid.upid()).await?;
+        let status = client.get_task_status(&pve_upid.node, upid.upid()).await?;
         if !wait || !status.is_running() {
             break Ok(status);
         }
@@ -189,23 +170,14 @@ async fn read_task_log(
 ) -> Result<Vec<pve_api_types::TaskLogLine>, Error> {
     let (remotes, _) = pdm_config::remotes::config()?;
 
-    if upid.remote() != remote {
-        bail!(
-            "remote '{remote}' does not match remote in upid ('{}')",
-            upid.remote()
-        );
-    }
+    crate::api::verify_upid(&remote, RemoteType::Pve, &upid)?;
 
-    let pve = get_remote(&remotes, upid.remote())?;
+    let pve_upid = upid.pve_upid()?;
 
-    let pve_upid: PveUpid = upid
-        .upid()
-        .parse()
-        .map_err(|err| format_err!("invalid upid for PVE: {} - {err}", upid.upid()))?;
+    let remote = get_remote(&remotes, upid.remote())?;
+    let client = connect(remote)?;
 
-    let pve = connect(pve)?;
-
-    let response = pve
+    let response = client
         .get_task_log(&pve_upid.node, upid.upid(), download, limit, start)
         .await?;
 
-- 
2.47.3



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


  parent reply	other threads:[~2025-11-12  9:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  9:41 [pdm-devel] [PATCH datacenter-manager 0/7] PBS remotes: task API and task cache support Lukas Wagner
2025-11-12  9:41 ` [pdm-devel] [PATCH datacenter-manager 1/7] pdm-api-types: remote upid: add helpers for getting native UPID type Lukas Wagner
2025-11-12  9:41 ` [pdm-devel] [PATCH datacenter-manager 2/7] pbs-client: add bindings for task list, task status, task log Lukas Wagner
2025-11-12 20:23   ` Thomas Lamprecht
2025-11-12  9:41 ` [pdm-devel] [PATCH datacenter-manager 3/7] pdm-api-types: api: factor out schema definitions for task log params Lukas Wagner
2025-11-12  9:42 ` [pdm-devel] [PATCH datacenter-manager 4/7] api: pbs tasks: add PBS task API Lukas Wagner
2025-11-12  9:42 ` Lukas Wagner [this message]
2025-11-12  9:42 ` [pdm-devel] [PATCH datacenter-manager 6/7] remote tasks: fetch/track PBS tasks Lukas Wagner
2025-11-12  9:42 ` [pdm-devel] [PATCH datacenter-manager 7/7] remote updates: re-enable PBS update fetching Lukas Wagner
2025-11-12 20:26   ` Thomas Lamprecht
2025-11-12 20:27 ` [pdm-devel] applied-series: [PATCH datacenter-manager 0/7] PBS remotes: task API and task cache support Thomas Lamprecht

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=20251112094203.112452-6-l.wagner@proxmox.com \
    --to=l.wagner@proxmox.com \
    --cc=pdm-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal