public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Lukas Wagner <l.wagner@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH cluster/ha-manager/manager v2 0/6] preparation for #6143: notification template cleanup
Date: Fri, 4 Apr 2025 20:27:06 +0200	[thread overview]
Message-ID: <eb4b0129-505e-4989-83a0-adee93e81656@proxmox.com> (raw)
In-Reply-To: <20250328101915.73951-1-l.wagner@proxmox.com>

Am 28.03.25 um 11:19 schrieb Lukas Wagner:
> With [#6143] on the horizon, notification templates, template variables
> and template helpers become part of our public API and as such
> we should provide some stability guarantees for them.
> As a result, we use this opportunity to do a 'final' cleanup.
> 
> This series:
>   - adds some common template vars for all notifications
>     - hostname
>     - fqdn
>     - cluster-name
>   - For HTML tables, we move the table generation to the handlebars template
>     instead of using the {{ table }} helper. This gives users a
>     better starting point for their changes (styling, structure).
>     The plaintext version still uses the helper, mostly due to the
>     fact that the helper automatically determines appropriate
>     column widths
>   - changes the names of some template variables for better clarity
>   - For fencing notifications, we stop dumping status data as JSON
>     to the notification and instead try to render it nicely, trying
>     to include all useful info from the former JSON dump
> 
> Bumps:
> 
> The patches for pve-manager and pve-ha-manager must depend on a bumped
> libpve-notify-perl due to the new 'PVE::Notify::common_template_data'
> helper.
> 
> Changes since v1:
>   - Use PVE::Tools::get_fqdn helper to get the FQDN (thx Thomas)
> 
> pve-cluster:
> 
> Lukas Wagner (1):
>   notify: add common_template_data
> 
>  src/PVE/Notify.pm | 27 +++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
> 
> 
> pve-manager:
> 
> Lukas Wagner (4):
>   notification templates: vzdump: generate HTML table in template
>   notifications: apt: clean up notification template
>   notification: replication: add common properties to template data
>   notifications: test: style fixup
> 
>  PVE/API2/APT.pm                               | 27 ++++++++-----------
>  PVE/API2/Replication.pm                       | 16 +++++------
>  PVE/VZDump.pm                                 | 21 +++++++--------
>  .../default/package-updates-body.html.hbs     | 15 ++++++++++-
>  .../default/package-updates-body.txt.hbs      |  2 +-
>  .../default/package-updates-subject.txt.hbs   |  2 +-
>  templates/default/replication-body.txt.hbs    |  2 +-
>  templates/default/test-body.html.hbs          |  2 +-
>  templates/default/vzdump-body.html.hbs        | 24 +++++++++++++++--
>  templates/default/vzdump-body.txt.hbs         |  2 +-
>  templates/default/vzdump-subject.txt.hbs      |  2 +-
>  11 files changed, 69 insertions(+), 46 deletions(-)
> 
> 
> pve-ha-manager:
> 
> Lukas Wagner (1):
>   notifications: overhaul fence notification
> 
>  src/PVE/HA/NodeStatus.pm                      | 43 +++++++++++++++----
>  src/PVE/HA/Sim/Env.pm                         |  8 ++--
>  src/templates/default/fencing-body.html.hbs   | 43 ++++++++++++++++---
>  src/templates/default/fencing-body.txt.hbs    | 40 +++++++++++++----
>  src/templates/default/fencing-subject.txt.hbs |  6 ++-
>  5 files changed, 111 insertions(+), 29 deletions(-)
> 
> 
> Summary over all repositories:
>   17 files changed, 207 insertions(+), 75 deletions(-)
> 


now applied all remaining patches, thanks!


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2025-04-04 18:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 10:19 [pve-devel] " Lukas Wagner
2025-03-28 10:19 ` [pve-devel] [PATCH pve-cluster v2 1/1] notify: add common_template_data Lukas Wagner
2025-04-04 10:15   ` [pve-devel] applied: " Thomas Lamprecht
2025-03-28 10:19 ` [pve-devel] [PATCH pve-manager v2 1/4] notification templates: vzdump: generate HTML table in template Lukas Wagner
2025-03-28 10:19 ` [pve-devel] [PATCH pve-manager v2 2/4] notifications: apt: clean up notification template Lukas Wagner
2025-03-28 10:19 ` [pve-devel] [PATCH pve-manager v2 3/4] notification: replication: add common properties to template data Lukas Wagner
2025-03-28 10:19 ` [pve-devel] [PATCH pve-manager v2 4/4] notifications: test: style fixup Lukas Wagner
2025-03-28 10:19 ` [pve-devel] [PATCH pve-ha-manager v2 1/1] notifications: overhaul fence notification Lukas Wagner
2025-04-04 18:25   ` [pve-devel] applied: " Thomas Lamprecht
2025-04-04 18:27 ` Thomas Lamprecht [this message]

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=eb4b0129-505e-4989-83a0-adee93e81656@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal