Feature Overview

Users need to be able to delete items that have been created for several reasons:

• If they have synced some content that has a security risk, they may want to ensure it is removed
• If they have synced some content that is broken, they may want to ensure its removed
• If they are paying for storage, they may want to reduce what is being stored

In addition we do not want to keep all snapshots around forever.  We should delete all snapshots that are older than some preconfigured time, likely 365 days for production, some smaller amount for stage (~90 days).  For now this does not need to be controlled on a per-org basis, but it may be nice to design this so it could be changed in the future.

Background and Strategic Fit

This provides some base level functionality that users likely expect with snapshotting.

Requirements

• Allow users to delete snapshots
• Warn users when deleting a snapshot that is currently in use by a template
• Should be able to delete snapshots of upload repositories and external repositories

• Automatically remove snapshots that are older than 365 days for production, 90 days for stage
• Show a warning on a template if it is using a snapshot approaching deletion (within 30 days?)

Use Cases (User Experience & Workflow)

A user would navigate to the Repositories application and navigate to the list of snapshots, from there a user could delete one or more snapshots.  

Documentation Considerations

• Document conditions in production when snapshots are deleted
• Document how to delete a snapshot