Open jepstein opened 1 year ago
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.
delete_after_days
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 https://github.com/mozilla/probe-scraper/pull/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 https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/754.
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_daysto 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 https://github.com/mozilla/probe-scraper/pull/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 https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/754.