From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 48AA31FF13E for ; Fri, 23 Jan 2026 15:35:08 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 05932FC02; Fri, 23 Jan 2026 15:35:04 +0100 (CET) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Fri, 23 Jan 2026 15:34:20 +0100 Message-ID: <20260123143454.150800-1-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1769178838885 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.017 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com, lxc.pm] Subject: [pve-devel] [PATCH-SERIES container/manager v3 0/8] api: restore: allow keeping not backed-up volumes X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" 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