From: Christian Ebner <c.ebner@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v4 5/7] api: add PUT endpoint for move_namespace
Date: Thu, 12 Mar 2026 17:19:04 +0100 [thread overview]
Message-ID: <21919711-1d05-4bf3-84ae-068e4c8371e4@proxmox.com> (raw)
In-Reply-To: <20260311151315.133637-6-h.laimer@proxmox.com>
One note inline.
On 3/11/26 4:13 PM, Hannes Laimer wrote:
> Requires DATASTORE_MODIFY on the parent of both the source and
> destination namespaces, matching the permissions used by
> create_namespace() and delete_namespace().
>
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
> src/api2/admin/namespace.rs | 78 ++++++++++++++++++++++++++++++++++++-
> 1 file changed, 76 insertions(+), 2 deletions(-)
>
> diff --git a/src/api2/admin/namespace.rs b/src/api2/admin/namespace.rs
> index ec913001..522133b1 100644
> --- a/src/api2/admin/namespace.rs
> +++ b/src/api2/admin/namespace.rs
> @@ -1,12 +1,16 @@
> use anyhow::{bail, Context, Error};
>
> use pbs_config::CachedUserInfo;
> -use proxmox_router::{http_bail, ApiMethod, Permission, Router, RpcEnvironment};
> +use proxmox_rest_server::WorkerTask;
> +use proxmox_router::{
> + http_bail, ApiMethod, Permission, Router, RpcEnvironment, RpcEnvironmentType,
> +};
> use proxmox_schema::*;
> +use serde_json::{json, Value};
>
> use pbs_api_types::{
> Authid, BackupGroupDeleteStats, BackupNamespace, NamespaceListItem, Operation,
> - DATASTORE_SCHEMA, NS_MAX_DEPTH_SCHEMA, PROXMOX_SAFE_ID_FORMAT,
> + DATASTORE_SCHEMA, NS_MAX_DEPTH_SCHEMA, PROXMOX_SAFE_ID_FORMAT, UPID_SCHEMA,
> };
>
> use pbs_datastore::DataStore;
> @@ -193,7 +197,77 @@ pub fn delete_namespace(
> Ok(stats)
> }
>
> +#[api(
> + input: {
> + properties: {
> + store: { schema: DATASTORE_SCHEMA },
> + ns: {
> + type: BackupNamespace,
> + },
> + "new-ns": {
> + type: BackupNamespace,
> + },
> + },
> + },
> + returns: {
> + schema: UPID_SCHEMA,
> + },
> + access: {
> + permission: &Permission::Anybody,
> + description: "Requires DATASTORE_MODIFY on the parent of 'ns' and on the parent of 'new-ns'.",
> + },
> +)]
> +/// Move a backup namespace (including all child namespaces and groups) to a new location.
> +pub fn move_namespace(
> + store: String,
> + ns: BackupNamespace,
> + new_ns: BackupNamespace,
> + rpcenv: &mut dyn RpcEnvironment,
> +) -> Result<Value, Error> {
> + let auth_id: Authid = rpcenv.get_auth_id().unwrap().parse()?;
> +
> + check_ns_modification_privs(&store, &ns, &auth_id)?;
> + check_ns_modification_privs(&store, &new_ns, &auth_id)?;
> +
> + let datastore = DataStore::lookup_datastore(&store, Some(Operation::Write))?;
Same note as for the previous patch, the operation parameter is now
non-optional and needs adaption.
> +
> + // Best-effort pre-checks for a fast synchronous error before spawning a worker.
> + if ns.is_root() {
> + bail!("cannot move root namespace");
> + }
> + if ns == new_ns {
> + bail!("source and target namespace must be different");
> + }
> + if !datastore.namespace_exists(&ns) {
> + bail!("source namespace '{ns}' does not exist");
> + }
> + if datastore.namespace_exists(&new_ns) {
> + bail!("target namespace '{new_ns}' already exists");
> + }
> + let target_parent = new_ns.parent();
> + if !datastore.namespace_exists(&target_parent) {
> + bail!("target parent namespace '{target_parent}' does not exist");
> + }
> + if ns.contains(&new_ns).is_some() {
> + bail!("cannot move namespace '{ns}' into its own subtree (target: '{new_ns}')");
> + }
> +
> + let worker_id = format!("{store}:{ns}");
> + let to_stdout = rpcenv.env_type() == RpcEnvironmentType::CLI;
> +
> + let upid_str = WorkerTask::new_thread(
> + "move-namespace",
> + Some(worker_id),
> + auth_id.to_string(),
> + to_stdout,
> + move |_worker| datastore.move_namespace(&ns, &new_ns),
> + )?;
> +
> + Ok(json!(upid_str))
> +}
> +
> pub const ROUTER: Router = Router::new()
> .get(&API_METHOD_LIST_NAMESPACES)
> .post(&API_METHOD_CREATE_NAMESPACE)
> + .put(&API_METHOD_MOVE_NAMESPACE)
> .delete(&API_METHOD_DELETE_NAMESPACE);
next prev parent reply other threads:[~2026-03-12 16:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 15:13 [PATCH proxmox-backup v4 0/7] fixes #6195: add support for moving groups and namespaces Hannes Laimer
2026-03-11 15:13 ` [PATCH proxmox-backup v4 1/7] datastore: add namespace-level locking Hannes Laimer
2026-03-12 15:43 ` Christian Ebner
2026-03-13 7:40 ` Hannes Laimer
2026-03-13 7:56 ` Christian Ebner
2026-03-17 13:03 ` Christian Ebner
2026-03-11 15:13 ` [PATCH proxmox-backup v4 2/7] datastore: add move_group Hannes Laimer
2026-03-12 16:08 ` Christian Ebner
2026-03-13 7:28 ` Hannes Laimer
2026-03-13 7:52 ` Christian Ebner
2026-03-11 15:13 ` [PATCH proxmox-backup v4 3/7] datastore: add move_namespace Hannes Laimer
2026-03-11 15:13 ` [PATCH proxmox-backup v4 4/7] api: add PUT endpoint for move_group Hannes Laimer
2026-03-12 16:17 ` Christian Ebner
2026-03-11 15:13 ` [PATCH proxmox-backup v4 5/7] api: add PUT endpoint for move_namespace Hannes Laimer
2026-03-12 16:19 ` Christian Ebner [this message]
2026-03-11 15:13 ` [PATCH proxmox-backup v4 6/7] ui: add move group action Hannes Laimer
2026-03-17 11:43 ` Christian Ebner
2026-03-17 11:48 ` Hannes Laimer
2026-03-11 15:13 ` [PATCH proxmox-backup v4 7/7] ui: add move namespace action Hannes Laimer
2026-03-12 16:21 ` [PATCH proxmox-backup v4 0/7] fixes #6195: add support for moving groups and namespaces Christian Ebner
2026-03-17 13:47 ` Christian Ebner
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=21919711-1d05-4bf3-84ae-068e4c8371e4@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=h.laimer@proxmox.com \
--cc=pbs-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox