From 4169f1b07cea561276d4051abd46aba98e0762ca Mon Sep 17 00:00:00 2001
From: James Tanner <tanner.jc@gmail.com>
Date: Fri, 8 Nov 2013 10:30:45 -0500
Subject: [PATCH] Revert "Fixes #4771 Add 1.4.x example of registered var
properties to the docsite"
This reverts commit dc74e700ce10295f38b953348cdea0d5b00bbb83.
---
docsite/rst/playbooks_variables.rst | 13 ++++---------
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst
index dbe3fa617f0..a2486fc510a 100644
--- a/docsite/rst/playbooks_variables.rst
+++ b/docsite/rst/playbooks_variables.rst
@@ -144,21 +144,16 @@ The following tasks are illustrative of how filters can be used with conditional
- debug: msg="it failed"
when: result|failed
+ # in most cases you'll want a handler, but if you want to do something right now, this is nice
+ - debug: msg="it changed"
+ when: result|changed
+
- debug: msg="it succeeded"
when: result|success
- debug: msg="it was skipped"
when: result|skipped
- # in most cases you'll want a handler, but if you want to do something right now, this is nice
- - debug: msg="it changed"
- when: result|changed
-
- # in 1.4 and above, properties of registered variables can be called as well;
- # eliminating the need to use filters in some cases.
- - debug: msg="it changed"
- when: result.changed
-
.. _forcing_variables_to_be_defined:
Forcing Variables To Be Defined