Remove Tenant Backup (Import / Export)
The feature is too heavy to implement speculatively.  If someone has a
concrete use case for it, driven by actual need and not supposition, we
can revisit design and implementation.
@@ -311,51 +311,4 @@ The key details of an audit log record are:
- If not, what role granted the privilege
-Tenant Backup and Restore
--------------------------
-
-An outcome of introducing multi-tenancy to SHIELD is that teams
-will now have data _inside_ SHIELD that they may wish to protect
-(i.e. backup and restore), and should be allowed to do so without
-affecting neighboring tenants.
-
-This is distinctly different from SHIELD operators performing
-full-SHIELD backup and restore operations to guard against
-disaster scenarios.
-
-To this end, we will need to write a custom target plugin for
-SHIELD tenants that will:
-
- - Save just their encryption keys
- - Save all tenant-owned data:
- - Schedules
- - Retention Policies
- - Target Configurations
- - Jobs
- - Tasks
- - Archives
- - (Custom) Storage Endpoints
- - Save references to any _globally shared_ storage
- configuration.
- - UUID
- - Name
- - Plugin
-
-If a tenant is not using any shared storage, the backup archives
-can always be restored (assuming a functional SHIELD).
-
-If a tenant _is_ using shared storage, restore operations will
-refuse to execute if any shared references are not found in the
-SHIELD. The algorithm for checking the existence of these
-resources works like this:
-
- 1. Check if a globally-shared storage endpoint exists with the
- given UUID; If so, nothing else needs to be updated.
- 2. Check if a globally-shared storage endpoint exists with the
- same name, and plugin; if so, update all references to the
- old UUID (as stored in the backup archive) to the new UUID.
- 3. Otherwise, halt the restore process (after checking
- suitability of other foreign references).
-
-
[enc]: https://github.com/starkandwayne/shield/blob/master/docs/encryption.md
