From 6742e5bf23457cd896236cb5beda69685f4a7b75 Mon Sep 17 00:00:00 2001
From: Weimin Yu <weiminyu@google.com>
Date: Tue, 2 May 2023 14:44:09 -0400
Subject: [PATCH] Remove CloudSql wipeout cron job in crash (#2017)

No more production data in crash. This allows us to repopulate crash
with test data.
---
 .../crash/default/WEB-INF/cloud-scheduler-tasks.xml  | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/core/src/main/java/google/registry/env/crash/default/WEB-INF/cloud-scheduler-tasks.xml b/core/src/main/java/google/registry/env/crash/default/WEB-INF/cloud-scheduler-tasks.xml
index 8f62ed02b..63f7d8ed3 100644
--- a/core/src/main/java/google/registry/env/crash/default/WEB-INF/cloud-scheduler-tasks.xml
+++ b/core/src/main/java/google/registry/env/crash/default/WEB-INF/cloud-scheduler-tasks.xml
@@ -158,16 +158,4 @@
     </description>
     <schedule>7 3 * * *</schedule>
   </task>
-
-  <!--
-    The next two wipeout jobs are required when crash has production data.
-   -->
-  <task>
-    <url><![CDATA[/_dr/task/wipeOutCloudSql]]></url>
-    <name>wipeOutCloudSql</name>
-    <description>
-      This job runs an action that deletes all data in Cloud SQL.
-    </description>
-    <schedule>7 3 * * 6</schedule>
-  </task>
 </taskentries>