Revert Changes on Connection Lost / Timeout Option - Feedback and Thoughts

[jwoodard80]

Welcome any thoughts or feedback on the below suggestion. If I am missing something and it is already in place please help me with finding this. :-)

I have multiple sites that am having to make several changes that could break access right there (Network address changes, Firewall changes, Routing, Etc.)  ........ I'm scared. HAHA!

The remote sites have 0.75% technical experience.... I was thinking about my MikroTik days and remember that if I happened to make a incorrect change that those changes would be reverted if I failed to connect back or didn't apply them within X time.

If this or anything like it sounds reasonable I would be happy to help test this

I was wondering if something similar couldn't be added here. It might not have to be enabled by default, but, could be enabled/disabled before someone attempted breaking changes.

Example:  Admin has to change a WAN IP

--- Working Correctly

     - Admin logs in and enables "Breaking Changes Mode" (Or whatever better name)
          -- The working config is immediately "snapshot or backed up"
          -- Working config is placed as the config to be used on reboot
          -- Timer Starts 
          -- Notification Alert shows at top
     - Admin makes changes just as they normally would
     - Tests changes and is happy with results
     - Disables "Breaking Changes Mode"
          -- Previous backed up config is then removed to prevent use on reboot.


--- Failed Change

     - Admin logs in and enables "Breaking Changes Mode" (Or whatever better name)
          -- The working config is immediately "snapshot or backed up"
          -- Working config is placed as the config to be used on reboot
          -- Notification Alert shows at top
     - Admin makes changes just as they normally would
     - Finds they have made a mistake and are unable to connect back to the GUI
     - Connection timer expires, or some other defined trigger
     - Breaking Changes Mode begins
          -- Previous Snapshot is automatically restored
          -- Router is Rebooted (if needed)
          -- Other actions such as logging the issue, etc...
     - Admin wait for completion of restore
     - Admin is able to start again, thankful they have not messed up and now having to make a multiple day trip