mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-04-20 17:31:24 -07:00
Fix M(). (#591)
* Fix M(). * Break long line. * Fix the remaining M(...). * Break long line.
This commit is contained in:
parent
e3d36a3408
commit
097aebadb0
126 changed files with 155 additions and 198 deletions
|
@ -16,8 +16,8 @@ description:
|
|||
- Users are roles with login privilege.
|
||||
- Groups are PostgreSQL roles usually without LOGIN privilege.
|
||||
- "Common use case:"
|
||||
- 1) add a new group (groups) by M(postgresql_user) module with I(role_attr_flags=NOLOGIN)
|
||||
- 2) grant them desired privileges by M(postgresql_privs) module
|
||||
- 1) add a new group (groups) by M(community.general.postgresql_user) module with I(role_attr_flags=NOLOGIN)
|
||||
- 2) grant them desired privileges by M(community.general.postgresql_privs) module
|
||||
- 3) add desired PostgreSQL users to the new group (groups) by this module
|
||||
options:
|
||||
groups:
|
||||
|
|
|
@ -105,7 +105,7 @@ notes:
|
|||
This could give unexpected results with manual created hba files, if it was improperly sorted.
|
||||
For example a rule was created for a net first and for a ip in that net range next.
|
||||
In that situation, the 'ip specific rule' will never hit, it is in the C(pg_hba) file obsolete.
|
||||
After the C(pg_hba) file is rewritten by the M(postgresql_pg_hba) module, the ip specific rule will be sorted above the range rule.
|
||||
After the C(pg_hba) file is rewritten by the M(community.general.postgresql_pg_hba) module, the ip specific rule will be sorted above the range rule.
|
||||
And then it will hit, which will give unexpected results.
|
||||
- With the 'order' parameter you can control which field is used to sort first, next and last.
|
||||
- The module supports a check mode and a diff mode.
|
||||
|
|
|
@ -15,7 +15,7 @@ short_description: Run PostgreSQL queries
|
|||
description:
|
||||
- Runs arbitrary PostgreSQL queries.
|
||||
- Can run queries from SQL script files.
|
||||
- Does not run against backup files. Use M(postgresql_db) with I(state=restore)
|
||||
- Does not run against backup files. Use M(community.general.postgresql_db) with I(state=restore)
|
||||
to run queries on files made by pg_dump/pg_dumpall utilities.
|
||||
options:
|
||||
query:
|
||||
|
|
|
@ -21,7 +21,7 @@ description:
|
|||
- The module allows to reset parameter to boot_val (cluster initial value) by I(reset=yes) or remove parameter
|
||||
string from postgresql.auto.conf and reload I(value=default) (for settings with postmaster context restart is required).
|
||||
- After change you can see in the ansible output the previous and
|
||||
the new parameter value and other information using returned values and M(debug) module.
|
||||
the new parameter value and other information using returned values and M(ansible.builtin.debug) module.
|
||||
options:
|
||||
name:
|
||||
description:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue