User Stories

The introduction of EE's posed some challenges for creating device configuration backups (where do you save the files?). This is a use case most customers deploy one way or another. It would be cool to have an out-of-the-box role that enable customers to create backups of their configs and store them in a destination they select, for example AWS S3 or a version control system like GitHub.

For this, we would need to leverage the config/backup module and then properly name the files when storing them in an object storage or tag them when publishing to a version control system, something like: ansible-collections/ansible.scm#176.

You should also be able to refer a specific date, which then translates to a file name or tag, to pull a specific config to restore. We could also have diff capabilities included to show any changes between two arbitrary configs.

Definition of Done

Should be agreed upon per team; add/remove/update to reflect:{}

• Tests are written and merged and successful
• DEV upstream code & tests merged
• DEV upstream documentation merged
• PM - all acceptance criteria are met
• cli_restore plugin in netcommon ANA-249
• This validated content collections are going to leverage the cli backup and restore plugins from netcommon. 
• ansible.scm functionality 
• Ref - Utilize https://github.com/network-automation/toolkit/tree/master/roles 
• Users should be able to create full backups/ backup when diff exists, save the back to local or remote data store(allowing tags). If required user should be able to restore these backups.