public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>
Cc: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox 14/29] notify: migrate PBS's and PVE's default matcher to expression syntax
Date: Fri, 24 Jul 2026 08:47:10 +0200	[thread overview]
Message-ID: <ncqyvodxnpdujx3eew6dqau2e4tfla4az6fcf4ffbsamrj3hgq@j3fvntfyqsrr> (raw)
In-Reply-To: <20260709115716.299836-15-l.wagner@proxmox.com>

On Thu, Jul 09, 2026 at 01:57:01PM +0200, Lukas Wagner wrote:
> Instead of providing the default matcher expression as a JSON blob, we
> programmatically construct the appropricate SectionConfigData entity.
> This required a change of the Context trait, now the default_config
> method returns &'static SectionConfigData instead of &'static str.
> 
> The actual SectionConfigData entity is only constructed once and then
> stored in a OnceLock.
> 
> A nice side-effect of this change is that the config-parsing code path
> is more efficient, since we don't have to deserialize the default config
> over and over again.
> 
one comment inline 
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
> ---
>  proxmox-notify/src/context/mod.rs      |  4 +-
>  proxmox-notify/src/context/pbs.rs      | 87 ++++++++++++++++++++------
>  proxmox-notify/src/context/pve.rs      | 67 +++++++++++++++-----
>  proxmox-notify/src/context/test.rs     |  9 ++-
>  proxmox-notify/src/lib.rs              |  6 +-
>  proxmox-notify/src/matcher/calendar.rs |  9 ++-
>  proxmox-notify/src/matcher/field.rs    | 11 +++-
>  proxmox-notify/src/matcher/severity.rs | 10 ++-
>  8 files changed, 157 insertions(+), 46 deletions(-)
> 
> diff --git a/proxmox-notify/src/context/mod.rs b/proxmox-notify/src/context/mod.rs
> index 87a2a716..70c3a567 100644
> --- a/proxmox-notify/src/context/mod.rs
> +++ b/proxmox-notify/src/context/mod.rs
> @@ -1,6 +1,8 @@
>  use std::fmt::Debug;
>  use std::sync::Mutex;
>  
> +use proxmox_section_config::SectionConfigData;
> +
>  use crate::Error;
>  use crate::renderer::TemplateSource;
>  
> @@ -24,7 +26,7 @@ pub trait Context: Send + Sync + Debug {
>      /// Proxy configuration for the current node
>      fn http_proxy_config(&self) -> Option<String>;
>      /// Return default config for built-in targets/matchers.
> -    fn default_config(&self) -> &'static str;
> +    fn default_config(&self) -> &'static SectionConfigData;
>      /// Return the path of `filename` from `source` and a certain (optional) `namespace`
>      fn lookup_template(
>          &self,
> diff --git a/proxmox-notify/src/context/pbs.rs b/proxmox-notify/src/context/pbs.rs
> index a9121548..b2561ad1 100644
> --- a/proxmox-notify/src/context/pbs.rs
> +++ b/proxmox-notify/src/context/pbs.rs
> @@ -1,14 +1,19 @@
>  use std::path::Path;
> +use std::sync::OnceLock;
>  
>  use serde::Deserialize;
>  use tracing::error;
>  
>  use proxmox_schema::{ObjectSchema, Schema, StringSchema};
> -use proxmox_section_config::{SectionConfig, SectionConfigPlugin};
> +use proxmox_section_config::{SectionConfig, SectionConfigData, SectionConfigPlugin};
>  
> -use crate::Error;
>  use crate::context::{Context, common};
> +use crate::endpoints::sendmail::{SENDMAIL_TYPENAME, SendmailConfig};
> +use crate::matcher::field::FieldMatcher;
> +use crate::matcher::severity::SeverityMatcher;
> +use crate::matcher::{MATCHER_TYPENAME, MatcherConfig};
>  use crate::renderer::TemplateSource;
> +use crate::{Error, Severity};
>  
>  const PBS_USER_CFG_FILENAME: &str = "/etc/proxmox-backup/user.cfg";
>  const PBS_NODE_CFG_FILENAME: &str = "/etc/proxmox-backup/node.cfg";
> @@ -60,21 +65,6 @@ fn lookup_mail_address(content: &str, username: &str) -> Option<String> {
>      }
>  }
>  
> -const DEFAULT_CONFIG: &str = "\
> -sendmail: mail-to-root
> -    comment Send mails to root@pam's email address
> -    mailto-user root@pam
> -
> -
> -matcher: default-matcher
> -    mode all
> -    invert-match true
> -    match-field exact:type=prune
> -    match-severity info
> -    target mail-to-root
> -    comment Route everything but successful prune job notifications to mail-to-root
> -";
> -
>  #[derive(Debug)]
>  pub struct PBSContext;
>  
> @@ -102,8 +92,67 @@ impl Context for PBSContext {
>          content.and_then(|content| common::lookup_datacenter_config_key(&content, "http-proxy"))
>      }
>  
> -    fn default_config(&self) -> &'static str {
> -        DEFAULT_CONFIG
> +    fn default_config(&self) -> &'static SectionConfigData {
> +        static DEFAULT_CONFIG: OnceLock<SectionConfigData> = OnceLock::new();
> +        DEFAULT_CONFIG.get_or_init(|| {
> +            // FIXME: Long-term we want to move the trait implementation to the product,
> +            // maybe add some nice builder to construct the default config.
> +            // Moving this as-is to the product would expose a lot of internals
> +            // to the product.
> +
> +            let mut config = SectionConfigData::default();
> +            config
> +                .set_data(
> +                    "mail-to-root",
> +                    SENDMAIL_TYPENAME,
> +                    SendmailConfig {
> +                        name: "mail-to-root".into(),
> +                        mailto_user: vec!["root@pam".into()],
> +                        comment: Some("Send mails to root@pam's email address".into()),
> +                        ..Default::default()
> +                    },
> +                )
> +                .expect("failed to set 'mail-to-root' in default config");
> +
> +            use proxmox_match_expression::{not, any_of, all_of};
> +
> +            let expression = any_of![
> +                not!(
> +                    FieldMatcher::Exact {
> +                        field: "type".into(),
> +                        values: vec!["prune".into()],
> +                    }.into()
> +                ),
> +                all_of![
> +                    FieldMatcher::Exact {
> +                        field: "type".into(),
> +                        values: vec!["prune".into()],
> +                    }.into(),
> +                    SeverityMatcher {
> +                        severities: vec![Severity::Error, Severity::Warning],
> +                    }.into(),
> +                ],
> +            ];
> +
> +            let expression = serde_json::to_string(&expression)
> +                .expect("failed serialize expression for 'default-matcher'");
> +
> +            config
> +                .set_data(
> +                    "default-matcher",
> +                    MATCHER_TYPENAME,
> +                    MatcherConfig {
> +                        name: "default-matcher".into(),
> +                        expression: Some(expression),
> +                        target: vec!["mail-to-root".into()],
> +                        comment: Some("Route everything but successful prune job notifications to mail-to-root".into()),
> +                        ..Default::default()
> +                    },
> +                )
> +                .expect("failed to set 'default-matcher' in default config");
> +
> +            config
> +        })
>      }
afaict the default changes from 'suppress prune info notifications'
to 'for prune notifications, only notify on error or warning'. not
very familiar with the notifications sent by PBS, i assume prune jobs
never send notice-level notifications? 
>  
>      fn lookup_template(
[...]




  reply	other threads:[~2026-07-24  6:47 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 11:56 [PATCH many 00/29] notifications: add nested match expressions Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 01/29] add new proxmox-match-expression crate Lukas Wagner
2026-07-24  6:46   ` Arthur Bied-Charreton
2026-07-09 11:56 ` [PATCH proxmox 02/29] notify: promote matcher to dir-style module Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 03/29] notify: fix doc comment Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 04/29] notify: matcher: break out severity matcher into submodule Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 05/29] notify: matcher: break out field " Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 06/29] notify: matcher: break out calendar " Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 07/29] notify: matcher: calendar: add basic unit test Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 08/29] notify: matcher: add InlineSeverityMatcher Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 09/29] notify: matcher: add InlineFieldMatcher Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 10/29] notify: matcher: add InlineCalendarMatcher Lukas Wagner
2026-07-24  6:47   ` Arthur Bied-Charreton
2026-07-24  9:43     ` Wolfgang Bumiller
2026-07-09 11:56 ` [PATCH proxmox 11/29] notify: matcher: add expression support Lukas Wagner
2026-07-24  6:59   ` Arthur Bied-Charreton
2026-07-09 11:56 ` [PATCH proxmox 12/29] notify: api: support new expression parameter Lukas Wagner
2026-07-24  6:46   ` Arthur Bied-Charreton
2026-07-24 10:01     ` Wolfgang Bumiller
2026-07-24 11:38       ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox 13/29] notify: api: add `get_matcher_as_expression` Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox 14/29] notify: migrate PBS's and PVE's default matcher to expression syntax Lukas Wagner
2026-07-24  6:47   ` Arthur Bied-Charreton [this message]
2026-07-09 11:57 ` [PATCH proxmox 15/29] notify: move legacy matcher keys behind feature flag Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 16/29] notification: increase matcher window width Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 17/29] notifications: matcher: add support for match expressions Lukas Wagner
2026-07-24  6:45   ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 18/29] notification: matcher: add better calendar editor Lukas Wagner
2026-07-24  6:46   ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 19/29] notifications: matcher: consistently use title case for UI elements Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 20/29] notification: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 21/29] api: notification: add 'migrate-to-expression' parameter to get_matcher Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 22/29] ui: notification: enable new matcher UI Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 23/29] notify: matcher: pass matcher config / updater directly Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 24/29] notify: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-07-24  6:48   ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 25/29] notify: add 'migrate_to_expression' parameter for get_matcher Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 26/29] api: notification: pass config/updater directly to rust bindings Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 27/29] api: notification: get_matcher: add 'migrate-to-expression' parameter Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 28/29] api: notification: add 'expression' to matcher parameter schema Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 29/29] ui: notification: enable new matcher UI Lukas Wagner
2026-07-24  6:44 ` [PATCH many 00/29] notifications: add nested match expressions Arthur Bied-Charreton
2026-07-24  6:53   ` Arthur Bied-Charreton

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=ncqyvodxnpdujx3eew6dqau2e4tfla4az6fcf4ffbsamrj3hgq@j3fvntfyqsrr \
    --to=a.bied-charreton@proxmox.com \
    --cc=l.wagner@proxmox.com \
    --cc=pbs-devel@lists.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