From 57cd65c401f37ed15befddfe3beabad3c4daafef Mon Sep 17 00:00:00 2001
From: Enric Tejedor Saavedra <enric.tejedor.saavedra@cern.ch>
Date: Wed, 30 Aug 2023 17:37:42 +0200
Subject: [PATCH] Propagate SWAN_DEV env variable to culler service

The culler service invokes check_ticket.sh, which invokes
eos_token.sh, which makes use of the SWAN_DEV variable to decide
on its behaviour.

Without this setting, the culler service does not get such
variable from the hub, even when it's set for a dev cluster.
---
 swan/files/swan_config.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/swan/files/swan_config.py b/swan/files/swan_config.py
index feab7b88..a1e32523 100644
--- a/swan/files/swan_config.py
+++ b/swan/files/swan_config.py
@@ -129,6 +129,7 @@ def swan_pod_hook(spawner, pod):
             "name": "cull-idle",
             "admin": True,
             "command": cull_cmd,
+            "environment": {'SWAN_DEV': os.environ.get('SWAN_DEV', 'false')}
         }
     )