Add VLAN Mapping feature to int_trunk_host interfaces

[skaszlik]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Add support for configuring VLAN mapping under trunk interfaces in the cisco.dcnm Ansible module. This feature, available starting from ND 4.1.1, allows users to utilize the int_trunk_host policy with two new keys: enableVlanMapping (boolean) and vlanMappingEntries (list of VLAN mapping configurations).

New or Affected modules(s):

• cisco.dcnm.dcnm_interface

Potential ansible task config

- name: Configure vlan map
  cisco.dcnm.dcnm_interface:
    fabric: "{{ fabric_name }}"
    state: merged
    config:
      - name: eth1/12
        type: eth
        switch:
          - "{{ ansible_switch1 }}"
        deploy: true
        profile:
          admin_state: true
          mode: trunk
          description: "ETH 1/12 Enable VLAN Mapping"
          enableVlanMapping: true
          vlanMappingEntries: "{"vlanMappingEntries":[{"customerVlan":"100","dot1qTunnel":"","customerInnerVlan":","providerVlan":"1000"}]}"

References

https://www.cisco.com/c/en/us/td/docs/dcn/nd/4x/articles-411/working-with-connectivity-for-lan-fabrics.html#_enable_vlan_mapping

Additional context
Add any other context or screenshots about the feature request here.