Interface ordering an port-channels

[dgjustice]

Environment

• Python version: yes
• netutils version: develop

@samuel-odinware pointed out that Arista puts port-channels at the head of the list when issuing a "show run" command. This is a potential problems when creating config diff's. I jumped on a Catalyst 9k (Cisco IOS XE Software, Version 17.03.03) in Cisco's sandbox and observed the same behavior. I will try to take a look at a fix early next week, but I wanted to raise an issue in case others are using this function.

...
interface Port-channel100
!
interface GigabitEthernet0/0
 description Management Interface - DO NOT TOUCH
 vrf forwarding Mgmt-vrf
 ip dhcp client client-id ascii cisco-acf5.e649.3680-Gi0/0
 ip address dhcp
 negotiation auto
!
interface GigabitEthernet1/0/1
 description Uplink to Sandbox Pod Network - DO NOT TOUCH
 switchport access vlan 4000
 switchport mode access
!
interface GigabitEthernet1/0/2
!
interface GigabitEthernet1/0/3
!
interface GigabitEthernet1/0/4
!
interface GigabitEthernet1/0/5
!
interface GigabitEthernet1/0/6
!

Observed Behavior

Steps to Reproduce

[itdependsnetworks]

Thanks, I secretly always presumed there will need to be "configurable" patterns as different vendors will order differently. I really didn't have a good idea how to tackle our what they differences actually are, but I think something we should consider.