You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be reasonable if port configuration in host config files would supersede global config thus allowing agile control over exclusions in port configuration.
The text was updated successfully, but these errors were encountered:
In cases of using switchport configuration in different yml files, e.g
group_vars/leafs.yml
host_vars/10.2.200.68.yml
configuration in group_vars is completely ignored - only configuration from host_vars is applied
TASK [arista.eos-bridging : Arista EOS switchport resources (Ansible >= 2.2)] **
ok: [10.2.200.68] => (item={u'access_vlan': 4010, u'name': u'Ethernet2', u'mode': u'access'})
ok: [10.2.200.69] => (item={u'access_vlan': 4011, u'name': u'Ethernet2', u'mode': u'access'})
ok: [10.2.200.68] => (item={u'access_vlan': 4010, u'name': u'Ethernet6', u'mode': u'access'})
ok: [10.2.200.69] => (item={u'access_vlan': 4011, u'name': u'Ethernet6', u'mode': u'access'})
ok: [10.2.200.69] => (item={u'access_vlan': 4011, u'name': u'Ethernet10', u'mode': u'access'})
ok: [10.2.200.68] => (item={u'access_vlan': 4010, u'name': u'Ethernet10', u'mode': u'access'})
It would be reasonable if port configuration in host config files would supersede global config thus allowing agile control over exclusions in port configuration.
The text was updated successfully, but these errors were encountered: