Yang model changes for Anchor prefix

Files modified/added
1. setup.py: added the bgp_prefix_list.yang to the setup list
2. sonic-bgp-prefix-list.yang: new yang model for the prefix list which is added in configdb through cli
3. test files to test the yang model

Signed-off-by: Mukul Chodhary <70460358+Muckthebuck@users.noreply.github.com>

Author: Muckthebuck

src/sonic-yang-models/doc/Configuration.md

@@ -94,6 +94,7 @@
   * [Static DNS](#static-dns)
   * [ASIC_SENSORS](#asic_sensors)  
   * [SRv6](#srv6)
+  * [Prefix List](#prefix-list)
 * [For Developers](#for-developers)
   * [Generating Application Config by Jinja2 Template](#generating-application-config-by-jinja2-template)
   * [Incremental Configuration by Subscribing to ConfigDB](#incremental-configuration-by-subscribing-to-configdb)
@@ -2913,6 +2914,18 @@ An example is as follows:
 }
 ```
 
+### Prefix List
+Prefix list table stores a list of prefixes with type and prefix separated by `|`. The specific configuration for the prefix type are then rendered by the PrefixListMgr. Currently ANCHOR_PREFIX is supported to add RADIAN configuration.
+
+An example is as follows:
+```json
+{
+    "PREFIX_LIST": {
+        "ANCHOR_PREFIX|fc00::/48": {}
+    }
+}
+```
+
 ### FIPS
 
 The FIPS table introduces FIPS  configuration.

src/sonic-yang-models/setup.py

@@ -205,6 +205,7 @@ def run(self):
                          './yang-models/sonic-system-port.yang',
                          './yang-models/sonic-macsec.yang',
                          './yang-models/sonic-bgp-sentinel.yang',
+                         './yang-models/sonic-bgp-prefix-list.yang',
                          './yang-models/sonic-asic-sensors.yang',
                          './yang-models/sonic-bmp.yang',
                          './yang-models/sonic-xcvrd-log.yang',

src/sonic-yang-models/tests/files/sample_config_db.json

@@ -2852,6 +2852,10 @@
                 "action": "uN",
                 "decap_dscp_mode": "pipe"
             }
+        },
+        "PREFIX_LIST": {
+            "ANCHOR_PREFIX|10.0.0.0/8" : {},
+            "ANCHOR_PREFIX|FC00::/48" : {}
         }
     },
     "SAMPLE_CONFIG_DB_UNKNOWN": {

src/sonic-yang-models/tests/yang_model_tests/tests/bgp_prefix_list.json

@@ -0,0 +1,13 @@
+{
+    "BGP_PREFIX_LIST_WITH_VALID_IPV4_PREFIX": {
+        "desc": "Load BGP prefix list table with a valid IPv4 prefix"
+    },
+    "BGP_PREFIX_LIST_WITH_VALID_IPV6_PREFIX": {
+        "desc": "Load BGP prefix list table with a valid IPv6 prefix"
+    },
+    "BGP_PREFIX_LIST_WITH_INVALID_PREFIX": {
+        "desc": "Load BGP prefix list table with an invalid prefix",
+        "eStrKey": "InvalidValue",
+        "eStr": ["prefix"]
+    }
+}

src/sonic-yang-models/tests/yang_model_tests/tests_config/bgp_prefix_list.json

@@ -0,0 +1,40 @@
+{
+    "BGP_PREFIX_LIST_WITH_VALID_IPV4_PREFIX": {
+        "sonic-bgp-prefix-list:sonic-bgp-prefix-list": {
+            "sonic-bgp-prefix-list:PREFIX_LIST": {
+                "PREFIX_LIST_LIST": [
+                    {
+                        "name": "ANCHOR_PREFIX",
+                        "ip-prefix": "10.0.0.0/8"
+                    }
+                ]
+            }
+        }
+    },
+    "BGP_PREFIX_LIST_WITH_VALID_IPV6_PREFIX": {
+        "sonic-bgp-prefix-list:sonic-bgp-prefix-list": {
+            "sonic-bgp-prefix-list:PREFIX_LIST": {
+                "PREFIX_LIST_LIST": [
+                    {
+                        "name": "ANCHOR_PREFIX",
+                        "ip-prefix": "fc00::/48"
+                    }
+                ]
+            }
+        }
+    },
+    "BGP_PREFIX_LIST_WITH_INVALID_PREFIX": {
+        "sonic-bgp-prefix-list:sonic-bgp-prefix-list": {
+            "sonic-bgp-prefix-list:PREFIX_LIST": {
+                "PREFIX_LIST_LIST": [
+                    {
+                        "name": "ANCHOR_PREFIX",
+                        "ip-prefix": "invalid_prefix"
+                    }
+                ]
+            }
+        },
+        "eStrKey": "InvalidValue",
+        "eStr": ["prefix"]
+    }
+}

src/sonic-yang-models/yang-models/sonic-bgp-prefix-list.yang

@@ -0,0 +1,63 @@
+
+module sonic-bgp-prefix-list {
+
+    yang-version 1.1;
+
+    namespace "http://github.com/sonic-net/sonic-bgp-prefix-list";
+    prefix bgppl;
+
+    import sonic-types {
+        prefix stypes;
+    }
+
+    import sonic-extension {
+        prefix ext;
+    }
+
+    description "SONIC Device-specfifc BGP prefix lists data";
+
+    revision 2025-02-05 {
+        description "Initial revision.";
+    }
+
+    container sonic-bgp-prefix-list {
+
+        container PREFIX_LIST {
+
+            description "PREFIX_LIST part of config_db.json";
+
+            list PREFIX_LIST_LIST {
+
+                description "PREFIX_LIST part of config_db.json with prefix";
+
+                key "name ip-prefix";
+
+                leaf name {
+                    type string;
+                    description "Name of the prefix list";
+                }
+
+                leaf ip-prefix {
+                    type union {
+                        type stypes:sonic-ip4-prefix;
+                        type stypes:sonic-ip6-prefix;
+                    }
+                }
+
+                leaf family {
+
+                    /* family leaf needed for backward compatibility
+                       Both ip4 and ip6 address are string in IETF RFC 6021,
+                       so must statement can check based on : or ., family
+                       should be IPv4 or IPv6 according.
+                     */
+
+                    must "(contains(../ip-prefix, ':') and current()='IPv6') or
+                        (contains(../ip-prefix, '.') and current()='IPv4')";
+                    type stypes:ip-family;
+                }
+            }
+        }
+        /* end of PREFIX_LIST */
+    }
+}