Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Glossary Doc: deprecate the old "only_if:" format in favor of "when:" #3540

Merged
merged 1 commit into from
Jul 16, 2013
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 2 additions & 4 deletions docsite/latest/rst/glossary.rst
Original file line number Diff line number Diff line change
Expand Up @@ -227,9 +227,7 @@ Ansible uses JSON for return data from remote modules. This allows modules to b
only_if
+++++++

A conditional statement that decides if a task is going to be executed in a playbook based on whether if the following expression
given is true or false. The newer 'when_' statements provide a cleaner way to express conditionals, 'only_if' is an older
construct. Though it may be still be useful in advanced situations.
A deprecated form of the "when:" statement. It should no longer be used.

Library
+++++++
Expand Down Expand Up @@ -414,7 +412,7 @@ Ansible uses "Connection Plugins" to define types of available transports. Thes
When
++++

When statements (when_string, when_changed, when_boolean, when_integer, etc) are easier to write forms of the only_if conditional. They can be affixed to any task to make that task decide to run only when an expression involving variables or facts is actually true.
An optional conditional statement attached to a task that is used to determine if the task should run or not. If the expression following the "when:" keyword evaluates to false, the task will be ignored.

Van Halen
+++++++++
Expand Down