Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change key names to match ios template #816

Closed
centove opened this issue Oct 26, 2020 · 1 comment
Closed

change key names to match ios template #816

centove opened this issue Oct 26, 2020 · 1 comment

Comments

@centove
Copy link

centove commented Oct 26, 2020

ISSUE TYPE
  • Feature Idea
TEMPLATE USING

Value Filldown NAME (\S+)
Value Required SN (\d+)
Value ACTION (\w+)
Value PROTOCOL ([^any][\w+\d+]+)
Value SOURCE (host\s\d+.\d+.\d+.\d+|any|\d+.\d+.\d+.\d+/\d+)
Value PORT_MODIFIER (eq|gt|lt|neq|range)
Value PORT_RANGE ([(\S+\s\S+)]+)
Value DESTINATION (host\s\d+.\d+.\d+.\d+|any|\d+.\d+.\d+.\d+/\d+)
Value MODIFIER (.*)

Start
^.List\s+${NAME}(\s+[readonly])
^\s+${SN}\s+${ACTION}\s+${PROTOCOL}\s+${SOURCE}(\s+${PORT_MODIFIER})(\s${PORT_RANGE})\s+${DESTINATION}(\s+${MODIFIER})* -> Record


SAMPLE COMMAND OUTPUT

SUMMARY

Rename fields SN and NAME to LINE_NUM and ACL_NAME to have consistent keys between ios and eos outputs
so you don't wind up with a spaghetti mess of conditional code while processing the output from multiple devices.

@itdependsnetworks
Copy link
Contributor

Mistakes were made... we should have considered this from the start but it was not. That being said we have decided not to pursue these changes as there are many people expecting the current keys and it would be problematic to them.

Apologies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants