scrapli_cfg
Documentation: https://scrapli.github.io/scrapli_cfg
Source Code: https://github.com/scrapli/scrapli_cfg
Examples: https://github.com/scrapli/scrapli_cfg/tree/master/examples
scrapli_cfg makes merging or replacing device configurations over Telnet or SSH easy, all while giving you the scrapli behaviour you know and love.
Key Features:
- Easy: It's easy to get going with scrapli and scrapli-cfg -- check out the documentation and example links above, and you'll be managing device configurations in no time.
- Fast: Do you like to go fast? Of course you do! All of scrapli is built with speed in mind, but if you really
feel the need for speed, check out the
ssh2transport plugin to take it to the next level! All the "normal" scrapli transport plugin goodness exists here in scrapli-cfg too! - Great Developer Experience: scrapli_cfg has great editor support thanks to being fully typed; that plus thorough docs make developing with scrapli a breeze.
Requirements
MacOS or *nix1, Python 3.7+
scrapli_cfg's only requirements is scrapli.
1 Although many parts of scrapli do run on Windows, Windows is not officially supported
Installation
pip install scrapli-cfg
See the docs for other installation methods/details.
A simple Example
from scrapli import Scrapli
from scrapli_cfg import ScrapliCfg
device = {
"host": "172.18.0.11",
"auth_username": "scrapli",
"auth_password": "scrapli",
"auth_strict_key": False,
"platform": "cisco_iosxe"
}
with open("myconfig", "r") as f:
my_config = f.read()
with Scrapli(**device) as conn:
cfg_conn = ScrapliCfg(conn=conn)
cfg_conn.prepare()
cfg_conn.load_config(config=my_config, replace=True)
diff = cfg_conn.diff_config()
print(diff.side_by_side_diff)
cfg_conn.commit_config()
cfg_conn.cleanup()
Metadata
Release files for scrapli-cfg 2025.1.30
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| scrapli_cfg-2025.1.30.tar.gz | 37.3 kB | Without provenance | Details for scrapli_cfg-2025.1.30.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scrapli_cfg-2025.1.30-py3-none-any.whl | Python 3 | none | any | Details for scrapli_cfg-2025.1.30-py3-none-any.whl |
Total release size: 98.4 kB
Release files / scrapli_cfg-2025.1.30.tar.gz
| Download URL | scrapli_cfg-2025.1.30.tar.gz |
|---|---|
| Size | 37.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ed3b5743116d35d7d65f86d06dd7e74fcc509e1c8df6ddebffdeb7cebed13e8
|
|
BLAKE2b-256 checksum How to use checksums |
e4ba4e475aee50378af7975cd940b21d727040e14175cb065e8b10b65b0b6240
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Release files / scrapli_cfg-2025.1.30-py3-none-any.whl
| Download URL | scrapli_cfg-2025.1.30-py3-none-any.whl |
|---|---|
| Size | 61.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aaf0c5f52ed06ba0ffefa860ab947c96b663c98a96f38b90eac567d46906fdf4
|
|
BLAKE2b-256 checksum How to use checksums |
3ffd33837093aa3cbed2939ad662252f47c37c49787189806ea100c83bca6e36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Security for scrapli-cfg 2025.1.30
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.