Delayed, scheduled and cued push configs

Share your Config Push presets or discuss automation in general
Post Reply
Posts: 1
Joined: Thu Mar 18, 2021 5:33 am

Fri Mar 19, 2021 4:29 am


I'm not sure if this is possible or should belong in feature requests.

We have lots of remote sites that power up and down independently. It works out that having all the sites up at the same time almost never happens. This makes it difficult to schedule changes across all sites.
I want to be able to push a configuration change, and for the sites that are powered down, for it to push after the next discovery / backup cycle.
Further, if possible I'd like to be able to cue up the changes so that if a site has been down for some time, all the changes will sequentially be applied, bringing it up to the same configuration as the other sites.
User avatar
Posts: 1230
Joined: Sat Jun 25, 2016 12:33 pm

Wed Apr 07, 2021 12:21 am

Scheduled pushes are indeed possible.

There is however no retry mechanism if a push fails. There is also no way to "queue" failed pushes for a repush later. Those would indeed belong in the "Feature Requests" section :)

There will also be new API endpoints coming in one of the point releases after 2.1 which will expose all config push functions over the API, so you could at least use that to monitor if / when pushes fail to reschedule them on the failed devices for later yourself.
Post Reply