Open p-sherratt opened 2 years ago
I think this makes sense
Providing the user information about where intended changes in configuration have originated from. This would be of great help when maintaining larger configurations and a library of configuration templates.
For
Incremental/partial patch-based configuration changes, not just "big-bang" changes.
Tracking "negated" configuration items. For example if a cisco-style change is applied which under a specific interface sets "no ip proxy-arp", followed by another change to set "ip proxy-arp", there should only be a single configuration line as a result.
I think the current recommendation will be https://github.com/netdevops/hier_config
Environment
Proposed Functionality
No specific functionality is proposed but can be discussed as the use cases are considered.
Use Case
Use-cases include:
The demo output below is from my own tooling based on the Lark parsing toolkit, which I can share privately but consider to be PoC quality. The ideas may be used to enhance functionality in the netutils config parser.
Example
demo.py
output