6 commits

Author	SHA1	Message	Date
Pepe Barbe	4e833cf506	Initial commit of change of semantics for module ... The postgresql_user module has several drawbacks: * No granularity for privileges * PostgreSQL semantics force working on one database at time, at least for Tables. Which means that a single call can't remove all the privileges for a user, and a user can't be removed until all the privileges are removed, forcing a module failure with no way to work around the issue. Changes: * Added the ability to specify granular privileges for database and tables within the database * Report if user was removed, and add an option to disable failing if user is not removed.	2012-08-22 10:04:57 -05:00
Pepe Barbe	3dd2c0700f	Syntax change to make module compatible with Python 2.4	2012-08-17 10:37:02 -05:00
Michael DeHaan	7e9e29011e	Add encoding lines to python modules such that they can take unicode options if they are fed them, since the ... AnsibleModule stuff no longer base64 encodes for simplicity and speed reasons.	2012-08-02 21:29:10 -04:00
Michael DeHaan	0a3ebdb6d5	Module consistency and make daisy chaining work with invalid arguments detection.	2012-08-01 00:22:02 -04:00
Lorin Hochstein	dcd214a631	Use standard argument names in PostgreSQL modules ... passwd -> password loginpass -> login_password loginuser -> login_user loginhost -> login_host Add an example playbook that shows how to use the modules.	2012-07-29 12:52:14 -04:00
Lorin Hochstein	def1fa23f8	Add postgresql_db and postgresql_user module. ... These modules are based on the mysql_db and mysql_user modules. Currently, the postgresql_user module can only grant all permissions on a database, fine-grained access has not been implemented yet.	2012-07-26 17:05:04 -04:00