Environment
- Python version: 3.13
- Nautobot version: verified on 3.0.7, 3.1.7 (demo.nautobot.com) and 3.2.0b2 (next.demo.nautobot.com)
- nautobot-golden-config version: verified on both v3.0.3 and v3.0.7
Expected Behavior
After selecting one or more devices from the golden config Configuration Overview page (/plugins/golden-config/golden-config/), clicking the Execute dropdown and then selecting any Job (Compliance, Intended or Backup), golden config should carry the selected device(s) over to the job page, but it doesn’t.
The corresponding job /run/ page should open with the Device field already populated by the device(s) name selected in the Configuration Overview page.
Observed Behavior
After selecting one or more devices and clicking the Execute dropdown for any GC job, the corresponding job /run/ page opens with Device field completely empty.
Steps to Reproduce
- select one or more devices from the golden config Configuration Overview page
- click the Execute dropdown and then select any Job (Compliance, Intended or Backup)
Environment
Expected Behavior
After selecting one or more devices from the golden config Configuration Overview page (
/plugins/golden-config/golden-config/), clicking the Execute dropdown and then selecting any Job (Compliance, Intended or Backup), golden config should carry the selected device(s) over to the job page, but it doesn’t.The corresponding job
/run/page should open with theDevicefield already populated by the device(s) name selected in the Configuration Overview page.Observed Behavior
After selecting one or more devices and clicking the Execute dropdown for any GC job, the corresponding job
/run/page opens withDevicefield completely empty.Steps to Reproduce