Sudo support operational in both playbooks and main program.   Implementation could use some cleanup.

but this is more or less a mirror of what /bin/ansible does.  It also has a 'fire and
forget' mode if the poll interval is left off or set to 0.

src= parameters for template and copy operations can be relative to the playbook (for /usr/bin/ansible-playbook) or current directory (for /usr/bin/ansible)

Code needs cleanup, but works

as well as template files.  PLUS, variables are now expressed in playbooks without having
to know about the setup task, which means playbooks are simpler to read now.

to use multiple import statements to implement 'class' like behavior, and also to share
a common list of handlers between multiple patterns.

service module is installed by setup.py

all modules take a common parameter name.  But more or less we still work idempotently
in modules.

Update man pages. Fix formatting in playbook example. Also, YAML documents by definition start with '---', so I have added this to the example and the manpage

run things as multiple sets of users (if you want) in the same playbook.

module works differently now

starter manpage for modules

allow template file location to be passed into template & setup modules

module vs command module for restarting.  May be some bugs and requires the service to implement 'status' -- and probably some better error handling (i.e. return JSON with "failed" element if failed).

Improvements welcome.

override the host file in a playbook to load different groups
of hosts.

onchange events like Puppet's file providers do.

on the system for use in a later template module.   These values
could also be used for module-specific config.

as I figure out how logging/output might look.  A couple of major TODO features
also listed in the file.

this by having a changed=True/False in the JSON for these modules.  Added a note
so folks won't think we can only execute shell :)