From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 4573E1FF0A3 for ; Thu, 01 Oct 2026 11:00:16 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id AF649213A6; Thu, 01 Oct 2026 11:00:15 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 01 Oct 2026 11:00:11 +0200 Message-Id: Subject: superseded: [PATCH many 00/29] notifications: add nested match expressions From: "Lukas Wagner" To: "Lukas Wagner" , , X-Mailer: aerc 0.21.0-0-g5549850facc2-dirty References: <20260709115716.299836-1-l.wagner@proxmox.com> In-Reply-To: <20260709115716.299836-1-l.wagner@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1790845211824 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.401 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: EEZN2SITY44SDIQ64ILRDJLNS3ZM5W56 X-Message-ID-Hash: EEZN2SITY44SDIQ64ILRDJLNS3ZM5W56 X-MailFrom: l.wagner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Thu Jul 9, 2026 at 1:56 PM CEST, Lukas Wagner wrote: > NOTE: I have a couple of other patches planned for the notification stack= (**); > so I guess it would make sense wait a bit before applying this -- just to= avoid > too many version bumps and too much maintainer churn. > > This resolves a long-standing limitation of notification matchers. Up unt= il > now, notification match rules could only be one level deep, so one top-le= vel > combinator (all/any) and an arbitrary number of match rules as direct chi= ldren. > This severely limits which kind of matching behaviors can be represented. > superseded-by:=20 https://lore.proxmox.com/all/20261001083706.144246-1-l.wagner@proxmox.com/T= /#u