Comment to explain why we strip _ansible_notify specially

pull/13613/head
Toshio Kuratomi 9 years ago
parent 51cca87d67
commit 8ffc1fa838

@ -28,11 +28,13 @@ class ActionModule(ActionBase):
results = super(ActionModule, self).run(tmp, task_vars) results = super(ActionModule, self).run(tmp, task_vars)
results.update(self._execute_module(tmp=tmp, task_vars=task_vars)) results.update(self._execute_module(tmp=tmp, task_vars=task_vars))
# Remove special fields from the result, which can only be set # Remove special fields from the result, which can only be set
# internally by the executor engine. We do this only here in # internally by the executor engine. We do this only here in
# the 'normal' action, as other action plugins may set this. # the 'normal' action, as other action plugins may set this.
for field in ('ansible_notify',): #
# We don't want modules to determine that running the module fires
# notify handlers. That's for the playbook to decide.
for field in ('_ansible_notify',):
if field in results: if field in results:
results.pop(field) results.pop(field)

Loading…
Cancel
Save