Enhance router list view and config diffs for better workflow

[willodc]

Peering Manager version

v1.8.3

Feature type

Change to existing functionality

Proposed functionality

1. Add the config diff button to the routers list.
2. Add a copy button to the config diff view
   Stretch goals:
3. Add a status indicator flag if related peers have been altered since the last config update.
4. Add the option to write the latest diff to a file per router at two points.
   Configuration wise, add the option to choose the file directory for those files.
   file <router-name).proposed.diff
   If config diff is generated, save that proposed diff.
   file .pushed.diff
   if config update is shipped, save that config to that file.
   4a) Add the option to save diffs for multiple routers.
   4b) Add the option to commit diffs to a git repo

Use case

1. Reviewing changes per router requires to multiple clicks to pull a diff per router. Then return to the main router list and find the next router that needs an update. Adding buttons to the router list would save this time.

2. To copy and paste a config diff, the output must be manually selected and copied. Adding a copy button to the diff output would be very helpful.

3. Identifying routers that have and have not been updated will eliminate the need to manually identify routers that need updates. Big time saver.

4. Saving the output would make it easy to create external scripts for automating ticket updates.
   4a) There's no way to generate diffs for multiple routers now, so being able to generate them and save them to the files would be great.
   4b) Generating the diffs and committing them into a local git repo would be fantastic. This could be used to trigger external system updates (like ticketing systems, etc)

Database changes

You may need a field for the update flag, I haven't reviewed the schema to know for sure.

External dependencies

na