apply route-map and prefix-list only to nodes that have the BGP peering applied

[PieterL75]

I have a tenant with a vrf. That vrf has SVI's over 6 nodes.
one node forsees external BGP peerings and those are secured with route-map and prefix-lists.
I used the vrf/structured_config to define the routemap and prefix lists.

But now I see that those are applied to all nodes, and not only to the those with the BGP peering..

Is there a cleaner way to do this ? I don't like that orphaned config, as it looks like something was configured incorrect

[ClausHolbechArista]

For now the only way would be to use some inline-jinja to check if you are on one of the 6 nodes.

Written from memory, to may need some adjustment. Refer to Ansible docs for guidance.

structured_config: |-
  {% if inventory_hostname in ['node1', 'node2'] %}
  route_maps: ...
  {% elif %}
  null
  {% endif %}

We have implemented ipv4_prefix_list_catalog, but it is currently only used by l3_interfaces defined under the nodes.

We would like to implement similar "catalogs" of route-maps and other areas which will be applied when referred to under the BGP peers, peer-groups etc. So the route-maps and prefix-lists them selves would also get proper models in eos_designs.

[ClausHolbechArista]

BTW this structured config would go under the VRF, since structured config there is placed at the root of the eos_cli_config_gen model.

[PieterL75]

Looks promising.
thx for the fast feedback