Skip to content
This repository was archived by the owner on Apr 21, 2023. It is now read-only.

Automating data deletion through schema updates #591

@jepstein

Description

@jepstein

Need to first determine timing of deletion for each environment

Schedule for data deletion

In the case of both Glean and legacy-telemetry based studies, you will make use of delete_after_days to set deletion for each Rally project. This can be submitted via PR.

For Glean-based studies, you will need to modify https://github.com/mozilla/probe-scraper/blob/main/repositories.yaml#L229, setting this property to the appropriate setting for each Glean project. You can see a PR that was used to add a similar property at mozilla/probe-scraper#530

For Legacy telemetry based studies, it is a little more involved. You will need to modify each schema in https://github.com/mozilla-services/mozilla-pipeline-schemas and rebuild according to the README.md in the repository. You can see a PR that was used to add a similar property at mozilla-services/mozilla-pipeline-schemas#754.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions