From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 4BB851FF13A for ; Wed, 13 May 2026 05:09:06 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 29FE9357D0; Wed, 13 May 2026 05:09:06 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Subject: applied: [PATCH pve-network 1/1] sdn: api: route maps: fix json schema for match, set and exit-action Date: Wed, 13 May 2026 05:08:18 +0200 Message-ID: <177864169605.4078454.8832656841506987431.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260512134336.312909-1-s.hanreich@proxmox.com> References: <20260512134336.312909-1-s.hanreich@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778641597449 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: Q2M7VMCYTXHPKUE5Q73KRCEXXQBK7YF3 X-Message-ID-Hash: Q2M7VMCYTXHPKUE5Q73KRCEXXQBK7YF3 X-MailFrom: t.lamprecht@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 VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 12 May 2026 15:43:34 +0200, Stefan Hanreich wrote: > Add missing format_description to the value properties in match and > set property strings. Their exact format depends on the key set in the > property string. > > The 2 keys that can have a value in the exit-action both refer to the > order number of a route map entry, so change the type to the > pre-defined route map order type. Order is a u16, so fix the maximum > value to match the maximum accepted value by FRR. This is wrong in > the JSON schema, but is correct in the section config type. > > [...] Applied, thanks! [1/1] sdn: api: route maps: fix json schema for match, set and exit-action commit: ba48fb02862e819552631c54b824541396a8dba6