fix: Nextflow pod spec can now alter imagePullPolicy

InformaticsMatters · Sep 19, 2024 · 5d8ec10 · 5d8ec10
1 parent f7a5ec2
commit 5d8ec10
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 3 deletions.
diff --git a/roles/player/defaults/main.yaml b/roles/player/defaults/main.yaml
@@ -32,6 +32,7 @@ fp_parameter_file: parameters.yaml
 fp_image_registry: ''
 fp_image_name: informaticsmatters/fragmentor-player
 fp_image_tag: '1.2.0'
+fp_image_pull_policy: 'IfNotPresent'
 
 # The nextflow version to run.
 # The player image generally contains the 'latest' nextflow version.

diff --git a/roles/player/templates/configmap-nextflow-config.yaml.j2 b/roles/player/templates/configmap-nextflow-config.yaml.j2
@@ -11,11 +11,13 @@ metadata:
 data:
   config: |
     process {
+      pod = [
+        nodeSelector: 'informaticsmatters.com/purpose-fragmentor=yes',
 {% if all_image_preset_pullsecret_name|string|length > 0 %}
-      pod = [nodeSelector: 'informaticsmatters.com/purpose-fragmentor=yes', imagePullSecret: '{{ all_image_preset_pullsecret_name }}']
-{% else %}
-      pod = [nodeSelector: 'informaticsmatters.com/purpose-fragmentor=yes']
+        imagePullSecret: '{{ all_image_preset_pullsecret_name }}',
 {% endif %}
+        imagePullPolicy: '{{ fp_image_pull_policy }}'
+      ]
     }
     executor {
         name = 'k8s'