← All plugins
SCRAPLIbeta

Scrapli

Run CLI commands and push configuration to network devices — Cisco IOS-XE / NX-OS / IOS-XR, Arista EOS, Juniper JunOS — over SSH/Telnet via scrapli, with optional TextFSM (ntc-templates) parsing. The catalog's first Python-SDK plugin.

SDK
Python
Protocol
inflowv1
Actions
2
Version
v0.1.0
Runs on
Any inflowv1 host
Categories
DevOps and infrastructureUtility

Reach for it when

Network devices over SSH or Telnet — Cisco, Arista, Juniper — with optional TextFSM parsing.

The use people don't expect

With "Parse output" on, show ip interface brief stops being text and becomes rows. That's the difference between a flow that screen-scrapes and a flow that can branch on what it found.

A flow that uses it

Each one is a shape of flow, not a template to copy. Node names are the labels as they appear on the canvas; a name with a slash means either would do.

01

Change window with an agent reading the output

Starts withAn approved change request.

  1. SCRAPLI

    Captures the before state, parsed to structured rows.

  2. SCRAPLI

    Pushes the config lines in config mode.

  3. SCRAPLI

    Captures the after state. A failed command commits as output instead of stopping the flow, so the next node can branch on it.

  4. CLAUDE AGENT

    Compares before and after against the change request and says whether what happened is what was asked for.

  5. Human in the Loop

    Disagreement parks for a human, with the rollback lines already drafted.

What you getThe verification step that normally depends on somebody being awake and careful. Beta — platform coverage is provisional, so verify against your own devices first.

The reference, not the pitch

This page is about what the plugin is for. Every action, every connection field, the ports, the install one-liner and the caveats are in the catalog entry, which is the thing the maintainer updates.

Near it in the catalog