[PATCH manager/network/proxmox-ve-rs 0/3] Add tag as a match statement to route maps

[PATCH manager/network/proxmox-ve-rs 0/3] Add tag as a match statement to route maps

[Stefan Hanreich]

This patch series exposes the already implemented `match tag` FRR statement in
the UI. This seems to have been left out in the intial series due to failing to
add it to the API_SCHEMA enum and the error then proliferated from there.


proxmox-ve-rs:

Stefan Hanreich (1):
  sdn: route maps: add tag to API_SCHEMA

 proxmox-ve-config/src/sdn/route_map.rs | 1 +
 1 file changed, 1 insertion(+)


pve-network:

Stefan Hanreich (1):
  sdn: route maps: add tag as match statement

 src/PVE/Network/SDN/RouteMaps.pm | 1 +
 1 file changed, 1 insertion(+)


pve-manager:

Stefan Hanreich (1):
  sdn: route map panel: add tag as match statement

 www/manager6/sdn/RouteMapPanel.js | 7 +++++++
 1 file changed, 7 insertions(+)


Summary over all repositories:
  3 files changed, 9 insertions(+), 0 deletions(-)

-- 
Generated by murpp 0.11.0

[PATCH proxmox-ve-rs 1/3] sdn: route maps: add tag to API_SCHEMA

[Stefan Hanreich]

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

[PATCH pve-network 2/3] sdn: route maps: add tag as match statement

[Stefan Hanreich]

This has been initially left out from the API_SCHEMA in ve-rs, which
is why this has not been included here.

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 src/PVE/Network/SDN/RouteMaps.pm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/PVE/Network/SDN/RouteMaps.pm b/src/PVE/Network/SDN/RouteMaps.pm
index b2bf9eda..85072582 100644
--- a/src/PVE/Network/SDN/RouteMaps.pm
+++ b/src/PVE/Network/SDN/RouteMaps.pm
@@ -43,6 +43,7 @@ our $ROUTE_MAP_MATCH_FORMAT = {
             'metric',
             'local-preference',
             'peer',
+            'tag',
         ],
     },
     value => {
-- 
2.47.3

[PATCH pve-manager 3/3] sdn: route map panel: add tag as match statement

[Stefan Hanreich]

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 www/manager6/sdn/RouteMapPanel.js | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/www/manager6/sdn/RouteMapPanel.js b/www/manager6/sdn/RouteMapPanel.js
index 71464d435..5c4de47cb 100644
--- a/www/manager6/sdn/RouteMapPanel.js
+++ b/www/manager6/sdn/RouteMapPanel.js
@@ -396,6 +396,12 @@ Ext.define('PVE.sdn.RouteMapMatchValueField', {
                 xtype: 'proxmoxtextfield',
                 vtype: 'IP6Address',
             },
+            tag: {
+                xtype: 'proxmoxintegerfield',
+                minValue: 1,
+                maxValue: 2 ** 32 - 1,
+                step: 1,
+            },
             metric: {
                 xtype: 'proxmoxintegerfield',
                 minValue: 1,
@@ -442,6 +448,7 @@ const ROUTE_MAP_MATCH_ACTION_LABELS = {
     metric: gettext('Metric'),
     'local-preference': gettext('Local Preference'),
     peer: gettext('Peer'),
+    tag: gettext('Tag'),
 };
 
 Ext.define('PVE.sdn.RouteMapMatchField', {
-- 
2.47.3