k8s: Fix a bug when manifest file ends with '---' (#139)

Any kubernetes manifest file ending with '---' will generate an error when applied using 'k8s' module. Although this may not be 'legal' YAML, this is quite frequent, specially on helm's generated manifest files. migrated from ansible/ansible#59160 Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
ansible-collections · Jun 24, 2020 · 9fb808c · 9fb808c
1 parent 10b332d
commit 9fb808c
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/changelogs/fragments/59160_handle_none_def.yml b/changelogs/fragments/59160_handle_none_def.yml
@@ -0,0 +1,2 @@
+bugfixes:
+- raw - handle condition when definition is none (https://github.com/ansible/ansible/pull/59160).
diff --git a/plugins/module_utils/raw.py b/plugins/module_utils/raw.py
@@ -171,6 +171,8 @@ def execute_module(self):
 
         flattened_definitions = []
         for definition in self.resource_definitions:
+            if definition is None:
+                continue
             kind = definition.get('kind', self.kind)
             api_version = definition.get('apiVersion', self.api_version)
             if kind.endswith('List'):
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		bugfixes:
		- raw - handle condition when definition is none (https://github.com/ansible/ansible/pull/59160).