Are only standard-typed ACLs valid?

[ajmyyra]

Hi there,

I noticed that ACL functions under module/acl.go only returns standard-typed ACLs. One such example can be seen in https://github.com/aristanetworks/goeapi/blob/master/module/acl.go#L161 . Device configs aren't often like this and many can have extended ACLs without any specified type, i.e. ip access-list NAME instead of ip access-list standard NAME, or ip access-list payload NAME.

Is the goeapi code just lacking support for non-standard ACL types (and if this is the case, would you be interested in PR to fix this?), or are general-typed ACLs the only thing you'll consider to be valid?

[cheynearista]

@ajmyyra It's true the code is lacking support here. We typically let the field drive our development of functions to implement...and this appears to be one area the field has yet to need. If you've got a fix for it then by all means submit the PR! I'll be more than happy to review.