changing permissions of modules to 0644
Made URL an optional parameter
Added module to handle rabbit policies [1]

Used quite a bit of the existing rabbit modules provied by @chrishoffman.

[1] https://www.rabbitmq.com/parameters.html
Cleaned up docs just a smidge

Mostly added periods where missed, and corrected /vhost spacing.
use new airbrake API URL
The setting of params via dict or string by tags

Updated per @mpdehaan suggestions.
* Rather than passing in JSON, supply the policy options as a hash
  or string.
* Bumped version_added to 1.5.
Handled string/dict the ansible way
Added existing_only options to skip creating new files on receiver
Added -FF flag to rsync invocation in synchronize

The `-FF` option causes rsync to look for files in the source directory named `.rsync-filter` and uses them to filter directories underneath them. If no `.rsync-filter` files are found, the behavior is identical to the command run without the -FF option. This flag does not sync the .rsync-filter files themselves.

This change should be backwards compatible and not produce surprising behavior for users, since they are unlikely to create `.rsync-filter` files unintentionally.
Added note about .rsync-filter files, with example
Fixed a typo.
Optionally unarchive a file already on the remote machine
properly convert arg into boolean
If there is no tmp_src, don't modify the args
Added version_added
now handles default and allaows for either shorthand entry or specific
fields per entry section

the default option works both when added to entry or as stand alone.
Signed-off-by: Brian Coca <briancoca+dev@gmail.com>
rds module: add snapshot capabilities

Add the ability to create snapshots and restore from them
Make instance creation, deletion, restore, and snapshotting idempotent
(really helps testing a playbook if you can run it multiple times)
postgresql_user module: Gracefully handle ALTER ROLE on read-only postgres servers.
Downgraded module version_added.
Fix postgresql_user to understand PG namespaces

Previously postgresql_user quoted user supplied identifers to create
grant statements that look like this:

    GRANT SELECT on "tablename" to "user";

Which only works if the tablename is not in a namespace.  If you supply
a namespaced tabelname like "report.revenue" then it creates this
incorrect statement:

    GRANT SELECT on "report.revenue" to "user";

Which will not find the "revenue" table in the "report" namespace, but
will rather look for a table named "report.revenue" in the current
(default public) namespace.  The correct form is:

    GRANT SELECT on "report"."revenue" to "user";

This approach could have the unfortunate effect that code that
previously relied on the other behavior to grant privileges on tables
with periods in their names may now break.  PostgreSQL users
typically shouldn't name tables as such, and users can still access the
old behavior and use tablenames with periods in the if they must by
supplying their own quoting.