initial commit of boundary_meter module
made changes as requested by mpdehaan and added code to remove key and cert pem files on removal of meter
fixup appearances of config_directory, remove slash, remove hardcoded /etc/bprobe
as per mpdehaan, change string formatting to something that will work with python 2.4
Added redis config module (slave and flush)
new module that handles extended attributes on files
Signed-off-by: Brian Coca <briancoca+dev@gmail.com>
Changed action keyword to command
changed role path template to read all vars instead of just extra_vars
fixed vpc provisioning / clarified group_id usage
Minor cleanup of YAML Syntax documentation
Merge pull request #3628 from jlund/yaml-syntax

Minor cleanup of YAML Syntax documentation
Adding getstr mode to download an object into a variable
Only revoke GRANT OPTION when user actually has it

When revoking privileges from a user, the GRANT OPTION is always
revoked, even if the user doesn't have it. If the user exists, this
doesn't give an error, but if the user doesn't exist, it does:

mysql> GRANT ALL ON test.* TO 'test'@'localhost';
Query OK, 0 rows affected (0.00 sec)

mysql> REVOKE GRANT OPTION ON test.* FROM 'test'@'localhost';
Query OK, 0 rows affected (0.00 sec)

mysql> REVOKE GRANT OPTION ON test.* FROM 'test'@'localhost';
Query OK, 0 rows affected (0.00 sec)

mysql> REVOKE ALL ON test.* FROM 'test'@'localhost';
Query OK, 0 rows affected (0.00 sec)

mysql> REVOKE GRANT OPTION ON test.* FROM 'test'@'localhost';
ERROR 1141 (42000): There is no such grant defined for user 'test' on
host 'localhost'

Additionally, in MySQL 5.6 this breaks replication because of
http://bugs.mysql.com/bug.php?id=68892.

Rather than revoking the GRANT OPTION and catching the error, check if
the user actually has it and only revoke it when he does.
Pacman module: recursive remove support
fix: if a path is symlink and trying to chmod, OSError Exception will be raised.
changed apikey and apiid to api_key and api_id and noted that it is boundary tags not ansible tags as per mpdehaan
Proper support for RHEL/CentOS 5 (the only thing it needs now is to call python26)
stringify conditional before handing it to Jinja2 for evaluation.

This should fix simple conditionals like:

    when: ansible_selinux

While here add tests for ansible.utils.check_conditional() in
"jinja2_compare mode".
ansible-playbook can load extra vars from a file, with "@" syntax
Updated documentation.