From 527b50fc43e21e4a14fc266fe0bbd45385a85494 Mon Sep 17 00:00:00 2001
From: Zack Galbreath <zack.galbreath@kitware.com>
Date: Wed, 15 Jan 2025 09:50:51 -0500
Subject: [PATCH] Bug fix to get the new retry-trigger-job cron working

I tested this by disabling flux and applying the new YAML manually
---
 k8s/production/custom/retry-trigger-jobs/cron-jobs.yaml | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/k8s/production/custom/retry-trigger-jobs/cron-jobs.yaml b/k8s/production/custom/retry-trigger-jobs/cron-jobs.yaml
index a39a6a539..7f4263b20 100644
--- a/k8s/production/custom/retry-trigger-jobs/cron-jobs.yaml
+++ b/k8s/production/custom/retry-trigger-jobs/cron-jobs.yaml
@@ -13,7 +13,6 @@ spec:
       backoffLimit: 0
       template:
         spec:
-          serviceAccountName: retry-trigger-jobs
           restartPolicy: Never
           containers:
           - name: retry-trigger-jobs
@@ -25,6 +24,12 @@ spec:
                 memory: 50M
             args:
               - "2"
+            env:
+            - name: GITLAB_TOKEN
+              valueFrom:
+                secretKeyRef:
+                  name: delete-stale-branches-credentials
+                  key: gitlab-token
             envFrom:
               - configMapRef:
                   name: python-scripts-sentry-config