summaryrefslogtreecommitdiffstats
path: root/bin/ansible-playbook
diff options
context:
space:
mode:
authorJesse Rusak <jesse@semanticmachines.com>2015-04-04 22:37:14 +0200
committerJesse Rusak <me@jesserusak.com>2015-04-11 01:38:59 +0200
commit652cd6cd5e60879cac3e74088930de1fc603cdda (patch)
treefa89e2b8fd21e651eeede3623f7093c8ec117465 /bin/ansible-playbook
parentMerge pull request #10629 from bcoca/backup_local_exists (diff)
downloadansible-652cd6cd5e60879cac3e74088930de1fc603cdda.tar.xz
ansible-652cd6cd5e60879cac3e74088930de1fc603cdda.zip
Fix --force-handlers, and allow it in plays and ansible.cfg
The --force-handlers command line argument was not correctly running handlers on hosts which had tasks that later failed. This corrects that, and also allows you to specify force_handlers in ansible.cfg or in a play.
Diffstat (limited to 'bin/ansible-playbook')
-rwxr-xr-xbin/ansible-playbook3
1 files changed, 2 insertions, 1 deletions
diff --git a/bin/ansible-playbook b/bin/ansible-playbook
index 118a0198e4..3d6e1f9f40 100755
--- a/bin/ansible-playbook
+++ b/bin/ansible-playbook
@@ -97,7 +97,8 @@ def main(args):
help="one-step-at-a-time: confirm each task before running")
parser.add_option('--start-at-task', dest='start_at',
help="start the playbook at the task matching this name")
- parser.add_option('--force-handlers', dest='force_handlers', action='store_true',
+ parser.add_option('--force-handlers', dest='force_handlers',
+ default=C.DEFAULT_FORCE_HANDLERS, action='store_true',
help="run handlers even if a task fails")
parser.add_option('--flush-cache', dest='flush_cache', action='store_true',
help="clear the fact cache")