From: Lukas Wagner <l.wagner@proxmox.com>
To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: [PATCH proxmox v6 13/43] notify: api: support new expression parameter
Date: Mon, 2 Nov 2026 15:57:10 +0100 [thread overview]
Message-ID: <20261102145748.411817-14-l.wagner@proxmox.com> (raw)
In-Reply-To: <20261102145748.411817-1-l.wagner@proxmox.com>
Add support for the new 'expression' parameter to the add_matcher and
updater_matcher API functions. Also add some validation that won't allow
to create a configuration with both old properties and new the
'expression'.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>
Tested-by: Michael Köppl <m.koeppl@proxmox.com>
---
proxmox-notify/src/api/matcher.rs | 119 ++++++++++++++++++++++++++++++
proxmox-notify/src/matcher/mod.rs | 85 ++++++++++++++++++++-
2 files changed, 202 insertions(+), 2 deletions(-)
diff --git a/proxmox-notify/src/api/matcher.rs b/proxmox-notify/src/api/matcher.rs
index b2bf15ae..3713dfef 100644
--- a/proxmox-notify/src/api/matcher.rs
+++ b/proxmox-notify/src/api/matcher.rs
@@ -40,6 +40,10 @@ pub fn add_matcher(config: &mut Config, matcher_config: MatcherConfig) -> Result
super::ensure_unique(config, &matcher_config.name)?;
super::ensure_endpoints_exist(config, &matcher_config.target)?;
+ matcher_config
+ .ensure_valid()
+ .map_err(|err| http_err!(BAD_REQUEST, "invalid matcher config: {err}"))?;
+
config
.config
.set_data(&matcher_config.name, MATCHER_TYPENAME, &matcher_config)
@@ -83,6 +87,7 @@ pub fn update_matcher(
DeleteableMatcherProperty::InvertMatch => matcher.invert_match = None,
DeleteableMatcherProperty::Comment => matcher.comment = None,
DeleteableMatcherProperty::Disable => matcher.disable = None,
+ DeleteableMatcherProperty::Expression => matcher.expression = None,
}
}
}
@@ -115,11 +120,19 @@ pub fn update_matcher(
matcher.disable = Some(disable);
}
+ if let Some(expression) = matcher_updater.expression {
+ matcher.expression = Some(expression);
+ }
+
if let Some(target) = matcher_updater.target {
super::ensure_endpoints_exist(config, target.as_slice())?;
matcher.target = target;
}
+ matcher
+ .ensure_valid()
+ .map_err(|err| http_err!(BAD_REQUEST, "invalid matcher config: {err}"))?;
+
config
.config
.set_data(name, MATCHER_TYPENAME, &matcher)
@@ -150,8 +163,12 @@ pub fn delete_matcher(config: &mut Config, name: &str) -> Result<(), HttpError>
#[cfg(all(test, feature = "sendmail"))]
mod tests {
+ use proxmox_match_expression::Expression;
+
use super::*;
+
use crate::matcher::MatchModeOperator;
+ use crate::matcher::expression::NotificationMatcher;
fn empty_config() -> Config {
Config::new("", "").unwrap()
@@ -172,6 +189,11 @@ matcher: matcher2
.unwrap()
}
+ fn valid_expression_string() -> String {
+ let expr = Expression::<NotificationMatcher>::Constant(true);
+ serde_json::to_string(&expr).unwrap()
+ }
+
#[test]
fn test_update_not_existing_returns_error() -> Result<(), HttpError> {
let mut config = empty_config();
@@ -261,4 +283,101 @@ matcher: matcher2
Ok(())
}
+
+ #[test]
+ fn test_update_matcher_mutually_exclusive_with_expression() -> Result<(), HttpError> {
+ let mut config = config_with_two_matchers();
+ let digest = config.digest;
+
+ let proto = MatcherConfigUpdater {
+ expression: Some(valid_expression_string()),
+ ..Default::default()
+ };
+
+ let mut updater = proto.clone();
+ updater.match_field = Some(vec!["exact:foo=bar".parse().unwrap()]);
+
+ assert!(update_matcher(&mut config, "matcher1", updater, None, Some(&digest),).is_err());
+
+ let mut updater = proto.clone();
+ updater.match_calendar = Some(vec!["mon..sun 12-13".parse().unwrap()]);
+
+ assert!(update_matcher(&mut config, "matcher1", updater, None, Some(&digest),).is_err());
+
+ let mut updater = proto.clone();
+ updater.match_severity = Some(vec!["info,warning".parse().unwrap()]);
+
+ assert!(update_matcher(&mut config, "matcher1", updater, None, Some(&digest),).is_err());
+
+ Ok(())
+ }
+
+ #[test]
+ fn test_update_invalid_expression() -> Result<(), HttpError> {
+ let mut config = config_with_two_matchers();
+ let digest = config.digest;
+
+ assert!(
+ update_matcher(
+ &mut config,
+ "matcher1",
+ MatcherConfigUpdater {
+ expression: Some("invalid".into()),
+ ..Default::default()
+ },
+ None,
+ Some(&digest),
+ )
+ .is_err()
+ );
+
+ Ok(())
+ }
+
+ #[test]
+ fn test_add_mutually_exclusive_with_expression() -> Result<(), HttpError> {
+ let mut config = empty_config();
+
+ let proto = MatcherConfig {
+ name: "matcher3".into(),
+ expression: Some(valid_expression_string()),
+ ..Default::default()
+ };
+
+ let mut entity = proto.clone();
+ entity.match_field = vec!["exact:foo=bar".parse().unwrap()];
+
+ assert!(add_matcher(&mut config, entity).is_err());
+
+ let mut entity = proto.clone();
+ entity.match_severity = vec!["info,warning".parse().unwrap()];
+
+ assert!(add_matcher(&mut config, entity).is_err());
+
+ let mut entity = proto.clone();
+ entity.match_calendar = vec!["mon..sun 12-13".parse().unwrap()];
+
+ assert!(add_matcher(&mut config, entity).is_err());
+
+ Ok(())
+ }
+
+ #[test]
+ fn test_add_invalid_expression() -> Result<(), HttpError> {
+ let mut config = empty_config();
+
+ assert!(
+ add_matcher(
+ &mut config,
+ MatcherConfig {
+ name: "matcher2".into(),
+ expression: Some("invalid".into()),
+ ..Default::default()
+ }
+ )
+ .is_err()
+ );
+
+ Ok(())
+ }
}
diff --git a/proxmox-notify/src/matcher/mod.rs b/proxmox-notify/src/matcher/mod.rs
index 4a1beecf..12110e95 100644
--- a/proxmox-notify/src/matcher/mod.rs
+++ b/proxmox-notify/src/matcher/mod.rs
@@ -76,7 +76,7 @@ pub enum MatchModeOperator {
optional: true,
},
})]
-#[derive(Debug, Serialize, Deserialize, Updater, Default)]
+#[derive(Clone, Debug, Serialize, Deserialize, Updater, Default)]
#[serde(rename_all = "kebab-case")]
/// Config for notification matchers.
pub struct MatcherConfig {
@@ -148,7 +148,6 @@ impl MatcherConfig {
self.warn_about_invalid_configuration();
let expression = if let Some(expression_str) = &self.expression {
-
serde_json::from_str(expression_str).map_err(|err| {
Error::FilterFailed(format!("could not deserialize filter expression: {err:#}"))
})?
@@ -204,6 +203,86 @@ impl MatcherConfig {
}
}
+ /// Ensure the validity of this matcher.
+ pub(crate) fn ensure_valid(&self) -> Result<(), Error> {
+ self.ensure_no_ignored_properties()?;
+ self.ensure_valid_expression()?;
+
+ Ok(())
+ }
+
+ fn ensure_no_ignored_properties(&self) -> Result<(), Error> {
+ if self.expression.is_some() {
+ let conflicting_properties = self.properties_conflicting_with_expression();
+
+ if !conflicting_properties.is_empty() {
+ let joined = conflicting_properties.join(", ");
+ return Err(Error::Generic(format!(
+ "'expression' property is mutually exclusive with: {joined}"
+ )));
+ }
+ }
+
+ Ok(())
+ }
+
+ fn ensure_valid_expression(&self) -> Result<(), Error> {
+ if let Some(expression) = &self.expression {
+ match serde_json::from_str::<Expression<NotificationMatcher>>(expression) {
+ Ok(expr) => {
+ Self::verify_match_expression_constraints(&expr)?;
+ }
+ Err(err) => {
+ return Err(Error::Generic(format!(
+ "'expression' is not valid: {err:#}"
+ )));
+ }
+ }
+ }
+
+ Ok(())
+ }
+
+ /// Recursively walk expression nodes and verify any additional constraints on them:
+ ///
+ /// - all-of/any-of/one-of *must* have child nodes:
+ /// The generic proxmox-match-expression crates handles empty combinators just fine,
+ /// however, from a UX perspective, it makes sense to require them to have child nodes.
+ fn verify_match_expression_constraints(
+ expr: &Expression<NotificationMatcher>,
+ ) -> Result<(), Error> {
+ match expr {
+ Expression::AllOf(expressions) => {
+ if expressions.is_empty() {
+ return Err(Error::Generic(
+ "'expression' may not contain empty 'all-of' rule".to_string(),
+ ));
+ }
+ }
+ Expression::AnyOf(expressions) => {
+ if expressions.is_empty() {
+ return Err(Error::Generic(
+ "'expression' may not contain empty 'any-of' rule".to_string(),
+ ));
+ }
+ }
+ Expression::OneOf(expressions) => {
+ if expressions.is_empty() {
+ return Err(Error::Generic(
+ "'expression' may not contain empty 'one-of' rule".to_string(),
+ ));
+ }
+ }
+ _ => {}
+ }
+
+ for child_expression in expr.children() {
+ Self::verify_match_expression_constraints(child_expression)?;
+ }
+
+ Ok(())
+ }
+
fn warn_about_invalid_configuration(&self) {
if self.expression.is_some() {
let conflicting_properties = self.properties_conflicting_with_expression();
@@ -260,6 +339,8 @@ pub enum DeleteableMatcherProperty {
MatchSeverity,
/// Delete `mode`
Mode,
+ /// Delete `expression`
+ Expression,
/// Delete `target`
Target,
}
--
2.47.3
next prev parent reply other threads:[~2026-11-02 15:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 14:56 [PATCH many v6 00/43] notifications: add nested match expressions Lukas Wagner
2026-11-02 14:56 ` [PATCH proxmox v6 01/43] add new proxmox-match-expression crate Lukas Wagner
2026-11-02 14:56 ` [PATCH proxmox v6 02/43] notify: log which matchers matched on a notification Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 03/43] notify: promote matcher to dir-style module Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 04/43] notify: fix doc comment Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 05/43] notify: matcher: break out severity matcher into submodule Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 06/43] notify: matcher: break out field " Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 07/43] notify: matcher: break out calendar " Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 08/43] notify: matcher: calendar: add basic unit test Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 09/43] notify: matcher: add InlineSeverityMatcher Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 10/43] notify: matcher: add InlineFieldMatcher Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 11/43] notify: matcher: add InlineCalendarMatcher Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 12/43] notify: matcher: add expression support Lukas Wagner
2026-11-02 14:57 ` Lukas Wagner [this message]
2026-11-02 14:57 ` [PATCH proxmox v6 14/43] notify: api: add `get_matcher_as_expression` Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 15/43] notify: move legacy matcher keys behind feature flag Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 16/43] notify: matcher: don't allow empty field/severity matchers Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 17/43] notify: matcher: re-serialize expression on create/update Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 18/43] notify: matcher: ensure that field names match SAFE_ID_REGEX Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox v6 19/43] notify: matcher: expression: reject ambiguous field matchers Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-widget-toolkit v6 20/43] notifications: increase matcher window width Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-widget-toolkit v6 21/43] notifications: matcher: add support for match expressions Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-widget-toolkit v6 22/43] notifications: matcher: add better calendar editor Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-widget-toolkit v6 23/43] notifications: matcher: consistently use title case for UI elements Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-backup v6 24/43] notification: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-backup v6 25/43] api: notification: add 'migrate-to-expression' parameter to get_matcher Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-backup v6 26/43] ui: notification: enable new matcher UI Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-backup v6 27/43] docs: notifications: rework matcher sections, describe expression option Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-perl-rs v6 28/43] notify: move proxmox-notify bindings from common to pve-rs Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-perl-rs v6 29/43] notify: matcher: pass matcher config / updater directly Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-perl-rs v6 30/43] notify: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-perl-rs v6 31/43] notify: add 'migrate_to_expression' parameter for get_matcher Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-perl-rs v6 32/43] debian: document versioned break for PVE::RS::Notify changes Lukas Wagner
2026-11-02 14:57 ` [PATCH pve-cluster v6 33/43] notify: adapt to changed module prefix for PVE::RS::Notify Lukas Wagner
2026-11-02 14:57 ` [PATCH pve-cluster v6 34/43] cluster: move pvecfg node version helpers from qemu-server Lukas Wagner
2026-11-02 14:57 ` [PATCH common v6 35/43] tools: move version_cmp() helper " Lukas Wagner
2026-11-02 14:57 ` [PATCH manager v6 36/43] vzdump: adapt to changed module prefix for PVE::RS::Notify Lukas Wagner
2026-11-02 14:57 ` [PATCH manager v6 37/43] api: notification: pass config/updater directly to rust bindings Lukas Wagner
2026-11-02 14:57 ` [PATCH manager v6 38/43] api: notification: get_matcher: add 'migrate-to-expression' parameter Lukas Wagner
2026-11-02 14:57 ` [PATCH manager v6 39/43] api: notification: add 'expression' to matcher parameter schema Lukas Wagner
2026-11-02 14:57 ` [PATCH manager v6 40/43] ui: notification: enable new matcher UI Lukas Wagner
2026-11-02 14:57 ` [PATCH manager v6 41/43] api: notification: reject matchers with expression if not supported by all nodes Lukas Wagner
2026-11-02 14:57 ` [PATCH docs v6 42/43] notifications: rework matcher sections, describe expression option Lukas Wagner
2026-11-02 14:57 ` [PATCH proxmox-mail-forward v6 43/43] cargo: opt into legacy-matchers feature 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=20261102145748.411817-14-l.wagner@proxmox.com \
--to=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 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.