Python Network Automation Dry Runs with Nornir, Scrapli, and Netmiko
Python network automation often starts as a script and slowly becomes a change platform. Before that happens, it needs tests, dry runs, and guardrails.
NetDevOps BlogΒΆ
Testing Nautobot and NetBox Synchronization Jobs in CI
Source-of-truth automation is powerful because it changes the system that other automation trusts. That also makes it risky. A broken sync job can create bad devices, duplicate prefixes, wrong interface names, or stale custom fields.
Parsing Network CLI Output with TextFSM, TTP, jc, and netutils
APIs are great, but most networks still have a lot of operational truth hidden in CLI output. A useful NetDevOps pipeline can parse that output and test it like normal data.
Validating Network Intent with Pydantic, JSON Schema, YAML, and Jinja2
Network automation usually breaks before it touches a router. The failure is often bad input data: a missing VLAN ID, an interface name typo, a wrong site slug, or a template variable that nobody supplied.