community.postgresql.postgresql_membership module – Add or remove PostgreSQL roles from groups
Note
This module is part of the community.postgresql collection (version 2.4.2).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.postgresql
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.postgresql.postgresql_membership
.
Synopsis
Adds or removes PostgreSQL roles from groups (other roles).
Users are roles with login privilege.
Groups are PostgreSQL roles usually without LOGIN privilege.
Common use case:
add a new group (groups) by community.postgresql.postgresql_user module with role_attr_flags=NOLOGIN
grant them desired privileges by community.postgresql.postgresql_privs module
add desired PostgreSQL users to the new group (groups) by this module
Requirements
The below requirements are needed on the host that executes this module.
psycopg2
Parameters
Parameter |
Comments |
---|---|
Specifies the name of a file containing SSL certificate authority (CA) certificate(s). If the file exists, the server’s certificate will be verified to be signed by one of these authorities. |
|
Any additional parameters to be passed to libpg. These parameters take precedence. Default: |
|
Name of database to connect to. |
|
If Choices:
|
|
The list of groups (roles) that need to be granted to or revoked from target_roles. |
|
Host running the database. If you have connection issues when using Default: |
|
The password this module should use to establish its PostgreSQL session. Default: |
|
Path to a Unix domain socket for local connections. Default: |
|
The username this module should use to establish its PostgreSQL session. Default: |
|
Database port to connect to. Default: |
|
Switch to session_role after connecting. The specified session_role must be a role that the current login_user is a member of. Permissions checking for SQL commands is carried out as though the session_role were the one that had logged in originally. |
|
Specifies the file name of the client SSL certificate. |
|
Specifies the location for the secret key used for the client certificate. |
|
Determines whether or with what priority a secure SSL TCP/IP connection will be negotiated with the server. See https://www.postgresql.org/docs/current/static/libpq-ssl.html for more information on the modes. Default of Choices:
|
|
Membership state. state=present implies the groupsmust be granted to target_roles. state=absent implies the groups must be revoked from target_roles. state=exact implies that target_roles will be members of only the groups (available since community.postgresql 2.2.0). Any other groups will be revoked from target_roles. Choices:
|
|
The list of target roles (groups will be granted to them). |
|
If It makes sense to use Choices:
|
Attributes
Attribute |
Support |
Description |
---|---|---|
Support: full |
Can run in check_mode and return changed status prediction without modifying target. |
Notes
Note
The default authentication assumes that you are either logging in as or sudo’ing to the
postgres
account on the host.To avoid “Peer authentication failed for user postgres” error, use postgres user as a become_user.
This module uses
psycopg2
, a Python PostgreSQL database adapter. You must ensure thatpsycopg2
is installed on the host before using this module.If the remote host is the PostgreSQL server (which is the default case), then PostgreSQL must also be installed on the remote host.
For Ubuntu-based systems, install the
postgresql
,libpq-dev
, andpython-psycopg2
packages on the remote host before using this module.The ca_cert parameter requires at least Postgres version 8.4 and psycopg2 version 2.4.3.
See Also
See also
- community.postgresql.postgresql_user
The official documentation on the community.postgresql.postgresql_user module.
- community.postgresql.postgresql_privs
The official documentation on the community.postgresql.postgresql_privs module.
- community.postgresql.postgresql_owner
The official documentation on the community.postgresql.postgresql_owner module.
- PostgreSQL role membership reference
Complete reference of the PostgreSQL role membership documentation.
- PostgreSQL role attributes reference
Complete reference of the PostgreSQL role attributes documentation.
Examples
- name: Grant role read_only to alice and bob
community.postgresql.postgresql_membership:
group: read_only
target_roles:
- alice
- bob
state: present
# you can also use target_roles: alice,bob,etc to pass the role list
- name: Revoke role read_only and exec_func from bob. Ignore if roles don't exist
community.postgresql.postgresql_membership:
groups:
- read_only
- exec_func
target_role: bob
fail_on_role: false
state: absent
- name: >
Make sure alice and bob are members only of marketing and sales.
If they are members of other groups, they will be removed from those groups
community.postgresql.postgresql_membership:
group:
- marketing
- sales
target_roles:
- alice
- bob
state: exact
- name: Make sure alice and bob do not belong to any groups
community.postgresql.postgresql_membership:
group: []
target_roles:
- alice
- bob
state: exact
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Dict of granted groups and roles. Returned: if state=present Sample: |
|
List of executed queries. Returned: always Sample: |
|
Dict of revoked groups and roles. Returned: if state=absent Sample: |
|
Membership state that tried to be set. Returned: always Sample: |
Collection links
Issue Tracker Repository (Sources) Report an issue Communication