Feature(eos_designs) add feature to specify loopback for OSPF RID

[pvinci-arista]

Enhancement summary

ospf config stanza has a router_id key. This requires an IP address of an interface on the host for the entry.

# IPv4 Address
      router_id: <str>

Customers routinely use a specific interface for defining the RID. An ospf_router_id_source_interface: option that substitutes the address of the source interface. This would simplify configs and follow user practices.

Which component of AVD is impacted

eos_designs

Use case example

Configure OSPF RID without manually copying address info.

Describe the solution you would like

Customer that defines a specific RID for a given process ID.

This PR asks for a change to eos_designs, but it sits between eos_designs and eos_cli_config_gen. An eos_cli_config_gen key of ospf_rid_source_interface make sense from a usability perspective, but it is not a direct rendering to a config.

Describe alternatives you have considered

This can be done today by copying thr address of the interface to the router_id key

Additional context

No response

Contributing Guide

• I agree to follow this project's Code of Conduct

[github-actions]

This issue is stale because it has been open 90 days with no activity. The issue will be reviewed by a maintainer and may be closed