From: Hannes Laimer <h.laimer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 0/2] fixes #6195, add support for moving namespaces
Date: Wed, 3 Sep 2025 12:11:15 +0200 [thread overview]
Message-ID: <20250903101117.176280-1-h.laimer@proxmox.com> (raw)
Adds support for moving namespaces within a datastore.
- we don't create non-existing target namespaces
- we don't allow moving if a namespace with the same "name" already
exists. So given:
/a/b/c/x
/1/2/3/4/x
moving /1/2/3/4/x to /a/b/c/ is not allowed.
these are the only real restrictions. Of course moving itself into
sub-namespaces, exeeding depth limit or moving root are also not. But
those are not really artificial.
Hannes Laimer (2):
fix #6195: api: datastore: add endpoint for moving namespaces
fix #6195: ui: add button/window for moving a namespace
pbs-datastore/src/datastore.rs | 121 +++++++++++++++++++++++++++++++++
src/api2/admin/namespace.rs | 43 +++++++++++-
www/Makefile | 1 +
www/datastore/Content.js | 38 +++++++++++
www/window/NamespaceMove.js | 47 +++++++++++++
5 files changed, 248 insertions(+), 2 deletions(-)
create mode 100644 www/window/NamespaceMove.js
--
2.47.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2025-09-03 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 10:11 Hannes Laimer [this message]
2025-09-03 10:11 ` [pbs-devel] [PATCH proxmox-backup 1/2] fix #6195: api: datastore: add endpoint " Hannes Laimer
2025-09-03 10:40 ` Shannon Sterz
2025-09-03 10:49 ` Hannes Laimer
2025-09-03 10:11 ` [pbs-devel] [PATCH proxmox-backup 2/2] fix #6195: ui: add button/window for moving a namespace Hannes Laimer
2025-09-03 12:10 ` [pbs-devel] superseded: [PATCH proxmox-backup 0/2] fixes #6195, add support for moving namespaces Hannes Laimer
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=20250903101117.176280-1-h.laimer@proxmox.com \
--to=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 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.