Support for VLAN Access-List implementation: Adding VLAN Access_list in Yaml/ configs for AVD

Issue Type

[x] Template enhancement
[x] Role enhancement
[ ] Documentation enhancement (avd.sh)

Is your feature request related to a problem? Please describe.

At the moment, there is no support for adding VLAN Access_List configuration to group_vars configuration in ansible-avd [...]

Describe the solution you'd like

As a Network operations Engineer supporting multiple clients, we would like to add VLAN Access list to the YAML configuration which generates the intended configuration in ansible/ arista avd this can be added in group_vars inside either the SERVERS.yml or TENNANTS_NETWORKS.yml so that when the playbook is deployed to CVP we would have configurations for VLAN Access_List in place inside of the intended ├── configs │ └── empty └── structured_configs └── cvp └── cv_server_configlets.yml folders respectively. in AVD we are able to use these three files: SERVER.yml , FABRIC.yml and TENNANTS_NETWORKS.yml to create the VLAN, assign it to a server port and put it an IP address from AVD. However for the Access_List : ACL we do this manually from the CVP portal. Describe alternatives you've considered

Currently we are having to implement the ACL configuration manually from the CVP Portal and here is a representation of the outputted config:

STATIC-LEAF-PARIS-LAB-LF02-LR2-CONFIGLET.conf
configuration
!
interface Ethernet1
 description CUC
!
ip access-list acl-client-vlan727-in
permit icmp any any
permit tcp any any
permit udp any any
!
interface Vlan727
ip access-group acl-client-vlan727-in in
!

Additional context

We would like to Implement this inside of AVD by extending the eos_designs with an existing eos_cli_config_gen we plan to maintain the current data structure for implementing Accesss_list as described in the Arista AVD eos_cli_config_gen documantation for access_list: https://www.avd.sh/en/latest/roles/eos_cli_config_gen/#ip-extended-access-lists

access_lists:
  < access_list_name_1 >:
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"
      < sequence_id_2 >:
        action: "< action as string >"
  < access_list_name_2 >:
    sequence_numbers:
      < sequence_id_1 >:
        action: "< action as string >"

aristanetworks / avd

Support for VLAN Access-List implementation: Adding VLAN Access_list in Yaml/ configs for AVD #942