Closed
Bug 1890574
Opened 6 months ago
Closed 5 months ago
Add a simple utility to select a backup staging folder to `recovery` and initiate recovery
Categories
(Firefox :: Profile Backup, task, P3)
Firefox
Profile Backup
Tracking
()
RESOLVED
FIXED
127 Branch
Tracking | Status | |
---|---|---|
firefox127 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
Details
(Whiteboard: [fidefe-device-migration])
Attachments
(1 file)
We're going to be working on recovery before we dive full-bore into the single-file archive support. That means we have to simulate having decrypting and extracted the archive.
One way to do that is, after staging a backup, to clone it to a sibling folder under ProfD/backups/recovery
, and use that folder as the "recovery folder".
So this bug is about adding a utility to debug.html to do that cloning, and to initiate recovery.
Updated•6 months ago
|
Assignee | ||
Updated•6 months ago
|
Severity: -- → N/A
Priority: -- → P3
Assignee | ||
Updated•6 months ago
|
Summary: Add a simple utility to debug.html clone `staging` to `recovery` and initiate recovery → Add a simple utility to debug.html clone the last backup staging folder to `recovery` and initiate recovery
Assignee | ||
Comment 1•5 months ago
|
||
I think we can skip the rename for now and just have a folder picker open to let the developer choose a staging directory, regardless of the name.
Summary: Add a simple utility to debug.html clone the last backup staging folder to `recovery` and initiate recovery → Add a simple utility to select a backup staging folder to `recovery` and initiate recovery
Assignee | ||
Updated•5 months ago
|
Assignee: nobody → mconley
Assignee | ||
Comment 2•5 months ago
|
||
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/09ed5777460d
Add a simple utility to initiate backup recovery in the debug tool. r=backup-reviewers,kpatenio
Status: NEW → RESOLVED
Closed: 5 months ago
status-firefox127:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•