Adding a custom task

Any set of commands can become a Netpilot task. The --task label is recorded in the inventory; --commands points to the command files.

Example: NTP

1. Create command files for each vendor

   config/cisco/ntp.txt          ← Cisco commands
   config/cisco/ntp_pre.txt      ← show commands before (optional)
   config/cisco/ntp_post.txt     ← show commands after (optional)
   config/alcatel/ntp.txt        ← Alcatel commands

2. Test on one device

   python -m src --task NTP --commands ntp --ip 10.0.0.1 --vendor cisco

3. Preview without connecting

   python -m src --task NTP --commands ntp --devices config/devices.csv --dry-run

4. Roll out

   python -m src --task NTP --commands ntp --devices config/devices.csv --workers 20

File naming convention

File	Required	Purpose
config/{vendor}/{task}.txt	Yes	Commands to push
config/{vendor}/{task}_pre.txt	No	Show commands before push
config/{vendor}/{task}_post.txt	No	Verification commands after push
config/{vendor}/{role_suffix}/{task}.txt	No	Role override (takes priority)

Inventory tracking

The --task label creates a {TASK}_status and {TASK}_date column in INVENTORY/inventory.csv, so you can track rollout progress per task independently.