Module documentation should have options sorted

This commit is contained in:
Michael DeHaan 2012-11-03 18:52:59 -04:00
parent 61a4674413
commit 78669c57d5
5 changed files with 5 additions and 2 deletions

2
facter
View file

@ -29,7 +29,7 @@ description:
(U(https://github.com/puppetlabs/facter)) on the remote system, returning
JSON data that can be useful for inventory purposes.
version_added: "0.2"
options: []
options: {}
examples:
- code: ansible www.example.net -m facter
description: "Example command-line invocation"

2
ohai
View file

@ -29,7 +29,7 @@ description:
returns JSON inventory data.
I(Ohai) data is a bit more verbose and nested than I(facter).
version_added: "0.6"
options: []
options: {}
examples:
- code: ansible webservers -m ohai --tree=/tmp/ohaidata
description: "Retrieve I(ohai) data from all Web servers and store in one-file per host"

1
ping
View file

@ -27,6 +27,7 @@ description:
- A trivial test module, this module always returns 'pong' on successful
contact. It does not make sense in playbooks, but is useful from
C(/usr/bin/ansible)
options: {}
examples:
- code: ansible webservers -m ping
description: Test 'webservers' status

1
raw
View file

@ -4,6 +4,7 @@ DOCUMENTATION = '''
---
module: raw
short_description: Executes a low-down and dirty SSH command
options: {}
description:
- Executes a low-down and dirty SSH command, not going through the module
subsystem. This is useful and should only be done in two cases. The

1
setup
View file

@ -30,6 +30,7 @@ DOCUMENTATION = '''
---
module: setup
short_description: Gathers facts about remote hosts
options: {}
description:
- This module is automatically called by playbooks to gather useful
variables about remote hosts that can be used in playbooks. It can also be