From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES container/manager v3 0/8] api: restore: allow keeping not backed-up volumes
Date: Fri, 23 Jan 2026 15:34:20 +0100 [thread overview]
Message-ID: <20260123143454.150800-1-f.ebner@proxmox.com> (raw)
Changes in v3:
* Add some refactorings up front to avoid bloating the 'create' API
endpoint even more.
* Rebase on master and then on refactorings.
* Don't preserve all when API mp/rootfs parameters are given, and
rather also check volumes present in the backup.
* Require 'restore' parameter to be present when
'restore-safeguard-mp-volumes' is specified.
* Add POD for restore_keep_non_backup_volumes()
* Slightly improve log messages.
Previous submissions:
v2: https://lore.proxmox.com/pve-devel/20250211112045.37214-1-f.ebner@proxmox.com/
v1: https://lore.proxmox.com/pve-devel/20250205143554.87844-1-f.ebner@proxmox.com/
See container patch "api: restore: allow keeping not backed-up volumes"
for details.
container:
Fiona Ebner (7):
api: create: move delayed_mp_param variable closer to usage
api: create: reduce scope for $mp_param variable
api: create: factor out create_ct_determine_mp_param helper
run make tidy
api: create: create_ct_determine_mp_param: improve code style
api: create: get rid of $storage_only_mode variable
api: restore: allow keeping not backed-up volumes
src/PVE/API2/LXC.pm | 277 +++++++++++++++++++++++++++++++++-----------
1 file changed, 210 insertions(+), 67 deletions(-)
manager:
Fiona Ebner (1):
ui: restore: enable safeguarding of mount point volumes by default
www/manager6/window/Restore.js | 98 ++++++++++++++++++++--------------
1 file changed, 58 insertions(+), 40 deletions(-)
Summary over all repositories:
2 files changed, 268 insertions(+), 107 deletions(-)
--
Generated by git-murpp 0.5.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2026-01-23 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 14:34 Fiona Ebner [this message]
2026-01-23 14:34 ` [pve-devel] [PATCH container v3 1/8] api: create: move delayed_mp_param variable closer to usage Fiona Ebner
2026-01-23 14:34 ` [pve-devel] [PATCH container v3 2/8] api: create: reduce scope for $mp_param variable Fiona Ebner
2026-01-23 14:34 ` [pve-devel] [PATCH container v3 3/8] api: create: factor out create_ct_determine_mp_param helper Fiona Ebner
2026-01-23 14:34 ` [pve-devel] [PATCH container v3 4/8] run make tidy Fiona Ebner
2026-01-23 14:34 ` [pve-devel] [PATCH container v3 5/8] api: create: create_ct_determine_mp_param: improve code style Fiona Ebner
2026-01-23 14:34 ` [pve-devel] [PATCH container v3 6/8] api: create: get rid of $storage_only_mode variable Fiona Ebner
2026-01-23 14:34 ` [pve-devel] [PATCH container v3 7/8] api: restore: allow keeping not backed-up volumes Fiona Ebner
2026-01-23 14:34 ` [pve-devel] [PATCH manager v3 8/8] ui: restore: enable safeguarding of mount point volumes by default Fiona 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=20260123143454.150800-1-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-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