If for some reason you add any configuration for MLAG interfaces using ansible-eos-interfaces like in the following example - role will mess up configuration as ansible-eos-interfaces and ansible-eos-mlag will conflict with each other
interfaces:
name: Ethernet21
description: "MLAG"
enable: true
name: Ethernet22
description: "MLAG"
enable: true
changed: [10.2.200.68] => (item={u'enable': True, u'name': u'Ethernet21', u'description': u'MLAG'})
changed: [10.2.200.69] => (item={u'enable': True, u'name': u'Ethernet21', u'description': u'MLAG'})
failed: [10.2.200.69] (item={u'enable': True, u'name': u'Ethernet22', u'description': u'MLAG'}) => {"changed": false, "commands": ["configure session ansible_1542881846", "interface Ethernet22", "no channel-group", "end"], "failed": true, "item": {"description": "MLAG", "enable": true, "name": "Ethernet22"}, "msg": "matched error in response: no channel-group\r\n% Interface Ethernet22 is a member of the MLAG peer link Port-Channel22; channel-group status not changed\r\nnvoa-tstsw-02(config-s-ansibl-if-Et22)#"}
failed: [10.2.200.68] (item={u'enable': True, u'name': u'Ethernet22', u'description': u'MLAG'}) => {"changed": false, "commands": ["configure session ansible_1542881846", "interface Ethernet22", "no channel-group", "end"], "failed": true, "item": {"description": "MLAG", "enable": true, "name": "Ethernet22"}, "msg": "matched error in response: no channel-group\r\n% Interface Ethernet22 is a member of the MLAG peer link Port-Channel22; channel-group status not changed\r\nnvoa-tstsw-01(config-s-ansibl-if-Et22)#"}
In my opinion such conflicts must be specifically highlighted in role description
If for some reason you add any configuration for MLAG interfaces using ansible-eos-interfaces like in the following example - role will mess up configuration as ansible-eos-interfaces and ansible-eos-mlag will conflict with each other
interfaces:
changed: [10.2.200.68] => (item={u'enable': True, u'name': u'Ethernet21', u'description': u'MLAG'}) changed: [10.2.200.69] => (item={u'enable': True, u'name': u'Ethernet21', u'description': u'MLAG'}) failed: [10.2.200.69] (item={u'enable': True, u'name': u'Ethernet22', u'description': u'MLAG'}) => {"changed": false, "commands": ["configure session ansible_1542881846", "interface Ethernet22", "no channel-group", "end"], "failed": true, "item": {"description": "MLAG", "enable": true, "name": "Ethernet22"}, "msg": "matched error in response: no channel-group\r\n% Interface Ethernet22 is a member of the MLAG peer link Port-Channel22; channel-group status not changed\r\nnvoa-tstsw-02(config-s-ansibl-if-Et22)#"} failed: [10.2.200.68] (item={u'enable': True, u'name': u'Ethernet22', u'description': u'MLAG'}) => {"changed": false, "commands": ["configure session ansible_1542881846", "interface Ethernet22", "no channel-group", "end"], "failed": true, "item": {"description": "MLAG", "enable": true, "name": "Ethernet22"}, "msg": "matched error in response: no channel-group\r\n% Interface Ethernet22 is a member of the MLAG peer link Port-Channel22; channel-group status not changed\r\nnvoa-tstsw-01(config-s-ansibl-if-Et22)#"}
In my opinion such conflicts must be specifically highlighted in role description