Feature Request: Support for per user config backup based on changes detected

[ryanmerolle]

Workflow:

• Detect change on device & Trigger countdown (pass username, device name, timestamp) by:
  - Some sort of trigger like a log message
• Create & maintain a user_change_tracker dictionary with:
  - A username with active changes being tracked
  - A list of devices with changes detected
  - A default git message (that can be overwritten)
  - A countdown timer until auto-commit
• ENMS status page for change tracking
  - Override of commit message
  - Add additional time to the commit counter
  - Add / Remove device to change for a user
  - If associated to an existing user, Warn/Alert that who it changed from
  - Show Dictionary of users with devices associated to change tracker, current commit message, & current countdown
  - Set counter for a user to 0, thus commiting the git change
• When commit timer reaches 0:
  • Git Pull (to make sure local repo is up to date)
  • SCP or pull config using Ansible, Nornir, Salt, Napalm, etc for ALL devices in the user's dictionary
  • Git commit with the user's id & the current user dictionary's commit message
• Email:
  • Gitlab to send group commit summary email
  • or ENMS
    Future nice to have:
• Feature: Ability to split changes per user (Example: device-1 & device-2 associated to user-1 change-1 and device-3 associated to user-1 change-2)
  Notes: Not a super common event. Users should focus on one change at a time.