From: Michal Fox <me@dualfroz.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH guest-common 2/3] vzdump: notes template: mention pool variable in description
Date: Tue, 6 Oct 2026 07:50:50 +0000 [thread overview]
Message-ID: <20261006075051.7-3-me@dualfroz.com> (raw)
In-Reply-To: <20261006075051.7-1-me@dualfroz.com>
The notes template now also supports a {{pool}} variable, which is
replaced with the resource pool the guest is a member of.
Signed-off-by: Michal Fox <me@dualfroz.com>
---
Only the description changes, the variable itself is handled in
pve-manager (1/3).
src/PVE/VZDump/Common.pm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/PVE/VZDump/Common.pm b/src/PVE/VZDump/Common.pm
index 67a4cf4..1eee227 100644
--- a/src/PVE/VZDump/Common.pm
+++ b/src/PVE/VZDump/Common.pm
@@ -363,9 +363,9 @@ my $confdesc = {
type => 'string',
description => "Template string for generating notes for the backup(s). It can contain"
. " variables which will be replaced by their values. Currently supported are"
- . " {{cluster}}, {{guestname}}, {{node}}, and {{vmid}}, but more might be added in the"
- . " future. Needs to be a single line, newline and backslash need to be escaped as '\\n'"
- . " and '\\\\' respectively.",
+ . " {{cluster}}, {{guestname}}, {{node}}, {{pool}}, and {{vmid}}, but more might be"
+ . " added in the future. Needs to be a single line, newline and backslash need to be"
+ . " escaped as '\\n' and '\\\\' respectively.",
requires => 'storage',
maxLength => 1024,
optional => 1,
--
2.43.0
next prev parent reply other threads:[~2026-10-06 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 7:50 [PATCH manager/guest-common/docs 0/3] fix #5990: vzdump: notes template: add pool variable Michal Fox
2026-10-06 7:50 ` [PATCH manager 1/3] " Michal Fox
2026-10-06 7:50 ` Michal Fox [this message]
2026-10-06 7:50 ` [PATCH docs 3/3] vzdump: notes template: document " Michal Fox
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=20261006075051.7-3-me@dualfroz.com \
--to=me@dualfroz.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.