fix: KUBECONFIG is now required

InformaticsMatters · Sep 19, 2024 · f7a5ec2 · f7a5ec2
1 parent 8626a59
commit f7a5ec2
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/roles/player/defaults/main.yaml b/roles/player/defaults/main.yaml
@@ -8,8 +8,8 @@
 fp_play: SetMe
 
 # The user's kubernetes configuration file.
-# The user must set KUBECONFIG - we do not assume ~/.kube/config
-fp_kubeconfig_file: "{{ lookup('env', 'KUBECONFIG') }}"
+# The user must define this variable - we no-longer rely on KUBECONFIG.
+fp_kubeconfig_file: SetMe
 
 # The namespace that is expected to exist.
 fp_namespace: fragmentor

diff --git a/roles/player/tasks/main.yaml b/roles/player/tasks/main.yaml
@@ -14,6 +14,12 @@
     - k8s_auth_host|length > 0
     - k8s_auth_api_key|length > 0
 
+- name: Assert kubeconfig file is named
+  assert:
+    that:
+    - fp_kubeconfig_file|length > 0
+    - fp_kubeconfig_file!='SetMe'
+
 # Go...
 
 # There is no 'undeploy' fragmentation is a 'Job'