ansible

Commit Graph

Author	SHA1	Message	Date
Scott Sturdivant	40a6a6f911	Clarify that the encrypted param must also be set. While the encrypted parameter's documentation clearly states that it needs to be set, if you are focused on the password parameter's documentation, there's nothing to draw your attention to the fact that encrypted may also need to be set.	11 years ago
Richard C Isaacson	525e811d9b	Bulk update of choices=BOOLEANS to type='bool'	11 years ago
Kyle Kelley	70d8be5cc2	Fix expires	11 years ago
James Cammarata	c85b7d868b	Merge branch 'fix-postgres_user_to_understand_pg_namespaces' of https://github.com/alanfairless/ansible into alanfairless-fix-postgres_user_to_understand_pg_namespaces	11 years ago
James Cammarata	a570280b81	Merge branch 'postgres_alter_role' of https://github.com/jinnko/ansible into jinnko-postgres_alter_role Conflicts: library/database/postgresql_user	11 years ago
Arturs Vonda	df853fa92e	Added port documentation to postgresql_db and postgresql_user	11 years ago
Matthew Jones	3ddfc8d471	Allow strings containing single and double quotes to be used as passwords for postgres_user	11 years ago
Alan Fairless	927a30c404	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.	11 years ago
Jinn Koriech	57dc4fbea2	postgresql_user module: Gracefully handle ALTER ROLE on read-only postgres servers.	11 years ago
Jinn Koriech	fbb1018abe	Fix postgresql_user documentation render	11 years ago
Jinn Koriech	e1aa94896f	Add documentation for usage of encrypted postgresql passwords.	11 years ago
James Tanner	4f9aadcc07	Addresses #5023 Fix import comments	11 years ago
James Tanner	38edad70ac	Fixes #5023 Convert all modules to use new snippet import pattern	11 years ago
Michael DeHaan	4c35b7f380	There's a cleaner way to do this, commit to module formatter pending. Revert "No longer need to reference 'version_added' in docs for these, as this was quite a while ago." This reverts commit `ff0a41d446`.	11 years ago
Michael DeHaan	9e4d71203d	No longer need to reference 'version_added' in docs for these, as this was quite a while ago.	11 years ago
James Tanner	eccbd21a0d	Fix typo in postgresql_user module docstrings	11 years ago
jctanner	6336129f59	Merge pull request #4686 from bcoca/postgresql_user_pwds postgresql_user now supports users w/o a password, encrypted passwords and expiration	11 years ago
Steve Tjoa	de4b105e09	Changed parameter from 'user' to 'name' in the examples to coincide with the specs.	11 years ago
Brian Coca	9b8b79f1fd	updated to make note that password is required before v1.4 Signed-off-by: Brian Coca <briancoca+dev@gmail.com>	11 years ago
Brian Coca	0d9a6b63ea	updated docs Signed-off-by: Brian Coca <briancoca+dev@gmail.com>	11 years ago
Brian Coca	cdec70eeff	now supports users w/o a password, encrypted passwords and expiration Signed-off-by: Brian Coca <briancoca+dev@gmail.com>	11 years ago
Jan-Piet Mens	3404a0fc16	DOCS: standardize on EXAMPLES (a.k.a. Docs-JumboPatch JetLag Edition) Migrated all examples: in DOCUMENTATION=''' string to standalone EXAMPLES=''' string Added deprecation warning to moduledev.rst and remove deprecated example from it Fixed up a few typos and uppercased some acronyms. add consistency to how EXAMPLES are formatted	12 years ago
Michael DeHaan	a6006f3c0f	Docs standardization	12 years ago
Michael DeHaan	cd97a4cb14	Allow modules to be categorized, and also sort them when generating the documentation.	12 years ago

24 Commits (3d2b201cf96fb376d6f89db4f29228dd039df282)