diff --git a/man/ansible-playbook.1.html b/man/ansible-playbook.1.html index 032b0aa1bc4..c6621b37d54 100644 --- a/man/ansible-playbook.1.html +++ b/man/ansible-playbook.1.html @@ -1,6 +1,6 @@ -
ansible-playbook — run an ansible playbook
Ansible playbooks are a configuration and multinode deployment system. Ansible-playbook is the tool +
ansible-playbook — run an ansible playbook
Ansible playbooks are a configuration and multinode deployment system. Ansible-playbook is the tool used to run them. See the project home page (link below) for more information.
ansible — run a command somewhere else
Ansible is an extra-simple tool/framework/API for doing 'remote things' over +
ansible — run a command somewhere else
Let’s test that module:
-../ansible/hacking/test-module ./rst/time time=\"March 14 12:23\"
+ansible/hacking/test-module ./time time=\"March 14 12:23\"
This should return something like:
{"changed": true, "time": "2012-03-14 12:23:00.000307"}
@@ -374,9 +374,9 @@ and guidelines:
To make it easier to write modules in bash and in cases where a JSON
module might not be available, it is acceptable for a module to return
key=value output all on one line, like this. The Ansible parser
-will know what to do.
-
-somekey=1 somevalue=two favcolor=red
+will know what to do:
+somekey=1 somevalue=2 rc=3 favcolor=red
+
If you’re writing a module in Python or Ruby or whatever, though, returning
JSON is probably the simplest way to go.