Collapse Cisco parsers #20
Labels
Enhancement
Enhance existing tool for end user.
Question
Maybe an issue, but more thought/discussion needed.
TODO
Changes to code generally transparent to end users.
Question
Should we collapse the Cisco type routers to one tool with options instead?
Is your enhancement request related to a problem? Please describe.
The configs between them are generally similar, there are outliers though (e.g, the wireless device configs). So this means much of the logic is the same between the parsers. When issues arise, we have to fix for multiple (unless it is forgotten) and usually this results in copy paste code. We may be able to do better.
Describe the solution you'd like
Explore collapsing the logic into a single parsing tool. I advise against a single monolithic parser, in favor of a multi-branch parser. This would allow the flexibility to give the end-user an option to explicitly specify which parser to leverage (e.g.,
--ios
,--nxos
, etc.). Also, this hopefully will allow logic re-use between the parsers in a cleaner manner.Describe alternatives you've considered
Current solution leverages multiple tools.
Additional context
None.
The text was updated successfully, but these errors were encountered: