What is Trigger?
Trigger is a robust network automation toolkit written in Python that was designed for interfacing with network devices and managing network configuration and security policy. It increases the speed and efficiency of managing large-scale networks while reducing the risk of human error.
Started by the AOL Network Security team in 2006, Trigger was originally designed for security policy management on firewalls, routers, and switches. It has since been expanded to be a full-featured network automation toolkit.
With the high number of network devices on the AOL network this application is invaluable to performance and reliability. We hope you'll find it useful on your network and consider participating!
Supported Platforms
- Cisco IOS, NX-OS, and ASA software
- Juniper Junos and ScreenOS
- Force10 router and switch platforms running FTOS
- Arista Networks 7000-family switches
- ... and more!
Refer to the official docs for the full list.
Key Features
Trigger is designed to work at scale and can support hundreds or thousands of network devices with ease. Here are some of things that make Trigger tick:
- Support for SSH, Telnet, and Juniper's Junoscript XML API.
- Easily get an interactive shell or execute commands asynchronously.
- Leverage advanced event-driven functionality to manage any number of jobs in parallel and handle output or errors as they return.
- Powerful metadata interface for performing complex queries to group and associate network devices by name, manufacturer, type, location, and more.
- Encrypted storage of login credentials so you can interact without constantly being prompted to enter your password.
- Flexible access-list & firewall policy parser that can test access if access is permitted, or easily convert ACLs from one format to another.
- Detailed support for timezones and maintenance windows.
- Import your metadata from an existing RANCID installation or a CSV file to get up-and-running quickly.
- A suite of tools for simplifying many common tasks.
Getting Started
The best way to get started is to read the documentation hosted by Read the Docs at https://trigger.readthedocs.io. There you will find everything you need to get going including usage examples, installation and configuration instructions, and more!
Python Version Requirements
Trigger v2.0.0+ requires Python 3.10 or 3.11. Python 3.12+ is not yet supported due to SimpleParse C extension compatibility issues.
Python 2.7 support ended with v1.6.0 (the last Python 2.7 compatible release).
Installation
# Install the latest version
pip install trigger
# Install in development mode
pip install -e ".[dev]"
# Using uv (faster)
uv pip install trigger
For users still requiring Python 2.7, use the v1.6.0 release:
pip install trigger==1.6.0
Development Setup
Contributing to Trigger? Set up pre-commit hooks to catch issues early:
# Install prek (fast pre-commit framework)
uv tool install prek # or: pip install prek
# Enable hooks in your clone
prek install
# Hooks will now run automatically on git commit
See CLAUDE.md for complete development documentation.
Upgrading from v1.6.0?
See the Migration Guide for detailed upgrade instructions.
Before you begin
- The main branch is the
primary branch for all development and releases. All pull requests target
main. - Each point release of Trigger is maintained as a tag. If you require a specific Trigger version, please refer to these.
Get in touch!
If you run into any snags, have questions, feedback, or just want to talk shop, please open an issue on GitHub Issues.
1 maintainer
Release files for trigger 2.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| trigger-2.3.1.tar.gz | 247.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trigger-2.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 496.8 kB
Release files / trigger-2.3.1.tar.gz
| Download URL | trigger-2.3.1.tar.gz |
|---|---|
| Size | 247.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39837909b96c99fbaf9a05d8f3e573a6fc538fb30c8f9df56bfbeb0c5c7a0588
|
|
BLAKE2b-256 checksum How to use checksums |
f8440ea5cbc79e346f2c93528d86cc2e989370debbcd230c6f7aabc5a81d781c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logRelease files / trigger-2.3.1-py3-none-any.whl
| Download URL | trigger-2.3.1-py3-none-any.whl |
|---|---|
| Size | 249.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
000bcdcb3a0474b5a45843896bcc1d3247bcd73512617329933bef1dbf450bdf
|
|
BLAKE2b-256 checksum How to use checksums |
712996012cdbeb4829bc8429dd983a5a1ce0d79fa5ee311e2edd28dbda46bcf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency log
