public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox-ve-rs 1/3] sdn: route maps: add tag to API_SCHEMA
Date: Wed, 13 May 2026 18:43:42 +0200	[thread overview]
Message-ID: <20260513164346.503049-2-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20260513164346.503049-1-s.hanreich@proxmox.com>

While present in the enum, this has been left out in the API_SCHEMA,
leading to the `match tag` statement being unavailable downstream.

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 proxmox-ve-config/src/sdn/route_map.rs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/proxmox-ve-config/src/sdn/route_map.rs b/proxmox-ve-config/src/sdn/route_map.rs
index 28328c7..d048469 100644
--- a/proxmox-ve-config/src/sdn/route_map.rs
+++ b/proxmox-ve-config/src/sdn/route_map.rs
@@ -422,6 +422,7 @@ impl ApiType for MatchAction {
                             "Match the next-hop to an IPv6 address.",
                         ),
                         EnumEntry::new("metric", "Match the metric of the route."),
+                        EnumEntry::new("tag", "Match the tag of the route."),
                         EnumEntry::new("local-preference", "Match the local preference."),
                         EnumEntry::new(
                             "peer",
-- 
2.47.3





  reply	other threads:[~2026-05-13 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 16:43 [PATCH manager/network/proxmox-ve-rs 0/3] Add tag as a match statement to route maps Stefan Hanreich
2026-05-13 16:43 ` Stefan Hanreich [this message]
2026-05-13 16:43 ` [PATCH pve-network 2/3] sdn: route maps: add tag as match statement Stefan Hanreich
2026-05-13 16:43 ` [PATCH pve-manager 3/3] sdn: route map panel: " Stefan Hanreich

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=20260513164346.503049-2-s.hanreich@proxmox.com \
    --to=s.hanreich@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