Shredder: handle lockwise deletion requests sent from Android
Categories
(Data Platform and Tools :: General, task, P2)
Tracking
(Not tracked)
People
(Reporter: mreid, Assigned: relud)
References
(Blocks 1 open bug)
Details
The "legacy" client id will be reported via Glean, but data will need to be deleted accordingly.
More detail in this PR:
https://github.com/mozilla-lockwise/lockwise-android/pull/1196
|
Reporter | |
Updated•4 years ago
|
|
Assignee | |
Comment 1•4 years ago
|
||
glean applications are automatically included in shredder runs as of 2020-05-20. PR: https://github.com/mozilla/bigquery-etl/pull/990
|
||
Comment 2•4 years ago
|
||
I can't quite tell from the linked PR... does this include handling the legacy telemetry client id stuffed in a UUID in the deletion-request pings?
|
|
Assignee | |
Comment 3•4 years ago
|
||
ah, no. legacy client ids are not yet handled.
|
|
Assignee | |
Comment 4•4 years ago
|
||
(In reply to Chris H-C :chutten from comment #2)
I can't quite tell from the linked PR... does this include handling the legacy telemetry client id stuffed in a UUID in the deletion-request pings?
bug 1658028 added support for deleting core and mobile-event pings in response to legacy client ids in deletion requests sent sent from certain glean products, including those in mozilla_lockbox_stable.deletion_request_v1.
does that cover what you were looking for?
|
|
||
Comment 5•4 years ago
|
||
I believe it does. Thank you!
Description
•