Changing the parameter names to be consistent, and adding root user

Changing the parameter names to be consistent, and adding root user default with empty password, as per mysql standard

Making inventory pattern matching handle group names

Git module ported to use module magic

fix trace-creating error in apt module - also make the default setting a...

the apt module to use it

added inventory_hostname_short varible

added a 'chdir' argument to the command module

the 'chdir' argument changes the current working directory to the
fullpath supplied as its value, before the execution of the command.

Output version string when --version is passed using optparse's version ...

env-setup no longer needs to be run from the ansible directory, it can b...

Fixes for OS X tests

as it is /bin/false on many systems but /usr/bin/false on OS X
test/playbook1.yml now just does command true, rather than command /bin/true,
again so that it works on OS X

Changed from using which false to just using command false to
make it simpler and also match how playbook1.yml works

Convert git module to module magic.
Drop cruft no longer needed.
Standardize indent to 4 spaces in methods switchLocalBranch, reset,
clone, and get_version.
Update is_local_branch to also handle '* branch' format.
Add is_current branch method()
Update pull() method to use is_current_branch()

env-setup now takes a -q argument to run in quiet mode

Rename: postgresql.yaml -> postgresql.yml

Postgres fixup

passwd -> password
loginpass -> login_password
loginuser -> login_user
loginhost -> login_host

Add an example playbook that shows how to use the modules.

The apt parameter changed from update-cache to update_cache, but
the error message still mentioned update-cache

Fixes for apt module

Tweak alias consistency a bit.  'package' has never been documented, but since it works, make it work in both places.
'name' is the preferred form.  Similarly, take 'name' for the 'guest' argument to the 'virt' module.

When sudoing to another user, the umask may be set such that the next user might not be able to read/execute
the file.  Deal with this.

If sudoing to a user other than root, the home directory of the original user is very unlikely to be readable by the
sudoed to user, so just use tmp.  Data will be readable by others (briefly before deletion) but never writeable.

An example of the new syntax:

vars_prompt:
 - name: 'secret_variable_name"
   prompt: "Enter secret value: "
   private: "yes"
 - name: "nonsecret_variable_name"
   prompt: "Enter non-secret value: "
   private: "no"

Add postgresql_db and postgresql_user module.