How tasks work

Netpilot is a generic config push engine. A task is any set of commands you push to devices — SNMPv3, syslog, NTP, ACL, banner, or anything else.

• --task is a label recorded in the inventory so you can track which devices have been configured for each task independently.
• --commands tells Netpilot which command files to load.

File layout per task

Each task uses up to 3 files per vendor:

File	Purpose	When
config/{vendor}/{task}_pre.txt	Show commands — snapshot before change	Before push
config/{vendor}/{task}.txt	Config commands to push	During push
config/{vendor}/{task}_post.txt	Show commands — verify change applied	After push

File resolution order

Most specific wins:

1. config/{vendor}/{role_suffix}/{task}.txt — role override (e.g. alcatel/poe_switch/snmpv3.txt)
2. config/{vendor}/{task}.txt — vendor default

Built-in tasks

Task	--commands	Files
SNMPv3 push	snmpv3	cisco/snmpv3.txt, alcatel/snmpv3.txt, alcatel/poe_switch/snmpv3.txt, alcatel_wlc/snmpv3.txt
Syslog config	syslog	cisco/syslog.txt, alcatel/syslog.txt
Config backup	backup	cisco/backup.txt, alcatel/backup.txt

Tip

Any task name works. Use --task NTP --commands ntp and create the corresponding ntp.txt files in each vendor folder.