Write a datareporting/state.json with the client ID that the recovered profile should ultimately have
Categories
(Firefox :: Profile Backup, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox127 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
Details
(Whiteboard: [fidefe-device-migration])
Attachments
(1 file)
Speaking with data science, the decision is to clone the client ID of the profile that is performing the recovery. We should write this file to datareporting/state.json at recovery time.
We'll definitely want a marionette test to ensure that the client ID is properly cloned after recovery.
|
||
Updated•2 months ago
|
|
Assignee | |
Updated•2 months ago
|
|
|
Assignee | |
Updated•2 months ago
|
|
|
Assignee | |
Comment 1•2 months ago
|
||
Data science wants us to copy the client IDs from whichever profile initiated recovery.
For legacy telemetry, the client ID is stored in a datareporting/state.json file.
This patch ensures that the client ID exists in the state.json file in the profile
that initiated recovery before then copying it over into the destination profile
for recovery.
This patch also updates the Marionette test to use a separate user profile to
initiate recovery from to ensure we get a unique client ID for it, compared to
the profile that the backup was created for.
Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0db7d7f15582 Clone the legacy client ID from the profile that initiated backup recovery. r=backup-reviewers,kpatenio
|
||
Comment 3•2 months ago
|
||
| bugherder | ||
Description
•