From 6f0c7b28db3f8a2701c4af4dfe7a2d691fc079ef Mon Sep 17 00:00:00 2001 From: Philip Jenvey Date: Thu, 3 Apr 2025 15:03:00 -0700 Subject: [PATCH] docs: update purge script's status now that it's running (#1679) Issue SYNC-4182 --- docs/tools/purge_old_records_tokenserver.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/tools/purge_old_records_tokenserver.md b/docs/tools/purge_old_records_tokenserver.md index da3e733c..3af15f53 100644 --- a/docs/tools/purge_old_records_tokenserver.md +++ b/docs/tools/purge_old_records_tokenserver.md @@ -9,11 +9,9 @@ Obsolete records are those replaced by newer records for the same user or marked --- ## Status -**DISABLED**: - - As of 2024-03-12, this script has not been running in an automated format. Requires a manual run to initiate. + - Running as Kubernetes Workload as part of deployment in `sync-prod` as: `tokenserver-prod-sync-app-1-purge-old-records-0` - See YAML configuration when editing each job. - See Kubernetes Engine Workload Panel in [`sync-prod`](https://console.cloud.google.com/kubernetes/workload/overview?inv=1&invt=AbmJeQ&project=moz-fx-sync-prod-3f0c) for more information. - - Each run is captured by an incrementing number after ` tokenserver-prod-sync-app-1-purge-old-records-<#>` ---