From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager v2 1/2] ui: remove handling of obsolete notification-policy/target settings
Date: Tue, 24 Jun 2025 13:28:16 +0200 [thread overview]
Message-ID: <20250624112817.132312-2-l.wagner@proxmox.com> (raw)
In-Reply-To: <20250624112817.132312-1-l.wagner@proxmox.com>
These were only used in the 'old' revamped notification stack which was
briefly available on pvetest. With PVE 9 we can finally get completely
rid of these.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
Notes:
Changes since v1:
- Rebased onto latest master (PVE 9)
www/manager6/dc/Backup.js | 16 ----------------
1 file changed, 16 deletions(-)
diff --git a/www/manager6/dc/Backup.js b/www/manager6/dc/Backup.js
index 3808aa25..5eb8b5fb 100644
--- a/www/manager6/dc/Backup.js
+++ b/www/manager6/dc/Backup.js
@@ -37,14 +37,6 @@ Ext.define('PVE.dc.BackupEdit', {
delete values.node;
}
- // Get rid of new-old parameters for notification settings.
- // These should only be set for those selected few who ran
- // pve-manager from pvetest.
- if (!isCreate) {
- Proxmox.Utils.assemble_field_data(values, { delete: 'notification-policy' });
- Proxmox.Utils.assemble_field_data(values, { delete: 'notification-target' });
- }
-
let selMode = values.selMode;
delete values.selMode;
@@ -158,14 +150,6 @@ Ext.define('PVE.dc.BackupEdit', {
let me = this;
let viewModel = me.getViewModel();
- // Migrate 'new'-old notification-policy back to old-old mailnotification.
- // Only should affect users who used pve-manager from pvetest. This was a remnant of
- // notifications before the overhaul.
- let policy = data['notification-policy'];
- if (policy === 'always' || policy === 'failure') {
- data.mailnotification = policy;
- }
-
if (data.exclude) {
data.vmid = data.exclude;
data.selMode = 'exclude';
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-06-24 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 11:28 [pve-devel] [PATCH pve-guest-common v2 1/1] backup job: remove 'notification-policy' and 'notification-target' options Lukas Wagner
2025-06-24 11:28 ` Lukas Wagner [this message]
2025-06-24 11:28 ` [pve-devel] [PATCH manager v2 2/2] ui: backup job details: show notification-mode instead of legacy keys Lukas Wagner
2025-07-08 18:07 ` Michael Köppl
2025-07-09 7:12 ` Lukas Wagner
2025-07-11 7:41 ` Michael Köppl
2025-07-08 18:17 ` Michael Köppl
2025-07-09 8:18 ` Lukas Wagner
2025-07-11 7:42 ` Michael Köppl
2025-07-08 18:20 ` [pve-devel] [PATCH pve-guest-common v2 1/1] backup job: remove 'notification-policy' and 'notification-target' options Michael Köppl
2025-07-09 8:20 ` [pve-devel] superseded: " Lukas Wagner
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=20250624112817.132312-2-l.wagner@proxmox.com \
--to=l.wagner@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 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.