peschmae/ansible-home-borr
1
0
Fork 0
Code Issues 5 Pull requests 38 Projects Releases Packages Wiki Activity Actions

chore(deps): update dependency community.postgresql to v5 #1019

Open
renovate-bot wants to merge 1 commit from renovate/community.postgresql-5.x into main
pull from: renovate/community.postgresql-5.x
merge into: peschmae:main
Conversation 0 Commits 1 Files changed 1 +1 -1
renovate-bot commented 2026-09-15 06:08:09 +00:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
community.postgresql galaxy-collection major 4.2.0 -> 5.0.0

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

ansible-collections/community.postgresql (community.postgresql)

v5.0.0

Compare Source

======

Release Summary

This is a major release of the community.postgresql collection.
This changelog contains all changes to the modules and plugins in this collection
that have been made after the previous release.

Minor Changes

  • Replace the deprecated ansible.module_utils.six compatibility shims with their Python standard library equivalents. ansible.module_utils.six is deprecated in ansible-core 2.21 and is scheduled for removal in 2.24.
  • postgresql_membership - add granted_by_any, at the top level and per memberships row, to manage every grant of a membership whoever made it, as the deprecated groups option does. GRANT then names no granting role, and state=absent and state=exact revoke every grant of the membership. On every version, groups of x is granted_by_any set with a memberships row of x.
  • postgresql_membership - add the grants and effective_options return values, listing every grant of the requested pairs and the options the target role effectively holds.
  • postgresql_membership - add the memberships option, one membership per row with its own target_roles, granted_by, admin_option, inherit_option and set_option, applied in one transaction. Mutually exclusive with groups; the top-level target_roles is the default for rows that name none (https://github.com/ansible-collections/community.postgresql/issues/757).
  • postgresql_membership - move PgMembership from the postgres module_utils into a new membership module_utils, split into PgMembershipByPair (the groups model) and PgMembershipByGrantor (the memberships model). External importers have to follow the move.
  • postgresql_membership - with memberships, check before emitting a GRANT that the connecting role has the privileges of the granting role and that the granting role holds ADMIN OPTION on the group, and fail naming the roles that do hold it. The deprecated groups option gets the privilege check for every granting role it finds recorded before it revokes. A task with nothing left to do is not checked.

Breaking Changes / Porting Guide

  • postgresql_membership - state=exact now reports granted with an entry for every requested group, as state=present does, so result.granted == {} no longer holds on an unchanged run.
  • postgresql_membership - a memberships row must set granted_by when the connecting role holds ADMIN OPTION on a group only through another role, since PostgreSQL refuses a grant recorded under a role without the option. The deprecated groups option is not affected.
  • postgresql_membership - on PostgreSQL 16 and later a memberships row manages the one grant recorded under its granting role, which is the bootstrap superuser when the connecting role is a superuser, the connecting role otherwise, or the role named by granted_by. state=present makes that grant even when another role has granted the membership, and state=absent and state=exact neither revoke nor report a grant recorded under another role. A task that was unchanged may report changed on its first run and fire its handlers. The deprecated groups option keeps treating the (group, target role) pair as the membership, whoever granted it (https://github.com/ansible-collections/community.postgresql/issues/757).

Deprecated Features

  • postgresql_membership - the top-level groups option is deprecated and will be removed in community.postgresql 6.0.0. granted_by_any with the groups key of memberships behaves the same on every version; target_roles stays at the top level, and an empty memberships list with state=exact replaces an empty groups list.

Removed Features (previously deprecated)

Bugfixes

  • postgresql_membership - fix state=absent and state=exact not removing a membership on PostgreSQL 16 and later when another role had granted it, and reporting a change on every run. The deprecated groups option now revokes every grant of the pair, one REVOKE per granting role, and fails naming the granting role when the connecting role lacks its privileges, where it used to succeed without revoking anything (https://github.com/ansible-collections/community.postgresql/issues/757).
  • postgresql_membership - fix a group named more than once being granted or revoked twice.
  • postgresql_membership - fix a group or role name containing a quote producing invalid SQL.
  • postgresql_membership - fix an empty target_roles list failing with a SQL syntax error; it is now a no-op.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [community.postgresql](https://github.com/ansible-collections/community.postgresql) | galaxy-collection | major | `4.2.0` -> `5.0.0` | --- > :warning: **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>ansible-collections/community.postgresql (community.postgresql)</summary> ### [`v5.0.0`](https://github.com/ansible-collections/community.postgresql/blob/HEAD/CHANGELOG.rst#v500) [Compare Source](https://github.com/ansible-collections/community.postgresql/compare/4.2.0...5.0.0) \====== ## Release Summary This is a major release of the `community.postgresql` collection. This changelog contains all changes to the modules and plugins in this collection that have been made after the previous release. ## Minor Changes - Replace the deprecated `ansible.module_utils.six` compatibility shims with their Python standard library equivalents. `ansible.module_utils.six` is deprecated in ansible-core 2.21 and is scheduled for removal in 2.24. - postgresql_membership - add `granted_by_any`, at the top level and per `memberships` row, to manage every grant of a membership whoever made it, as the deprecated `groups` option does. `GRANT` then names no granting role, and `state=absent` and `state=exact` revoke every grant of the membership. On every version, `groups` of `x` is `granted_by_any` set with a `memberships` row of `x`. - postgresql_membership - add the `grants` and `effective_options` return values, listing every grant of the requested pairs and the options the target role effectively holds. - postgresql_membership - add the `memberships` option, one membership per row with its own `target_roles`, `granted_by`, `admin_option`, `inherit_option` and `set_option`, applied in one transaction. Mutually exclusive with `groups`; the top-level `target_roles` is the default for rows that name none (https://github.com/ansible-collections/community.postgresql/issues/757). - postgresql_membership - move `PgMembership` from the `postgres` module_utils into a new `membership` module_utils, split into `PgMembershipByPair` (the `groups` model) and `PgMembershipByGrantor` (the `memberships` model). External importers have to follow the move. - postgresql_membership - with `memberships`, check before emitting a `GRANT` that the connecting role has the privileges of the granting role and that the granting role holds `ADMIN OPTION` on the group, and fail naming the roles that do hold it. The deprecated `groups` option gets the privilege check for every granting role it finds recorded before it revokes. A task with nothing left to do is not checked. ## Breaking Changes / Porting Guide - postgresql_membership - `state=exact` now reports `granted` with an entry for every requested group, as `state=present` does, so `result.granted == {}` no longer holds on an unchanged run. - postgresql_membership - a `memberships` row must set `granted_by` when the connecting role holds `ADMIN OPTION` on a group only through another role, since PostgreSQL refuses a grant recorded under a role without the option. The deprecated `groups` option is not affected. - postgresql_membership - on PostgreSQL 16 and later a `memberships` row manages the one grant recorded under its granting role, which is the bootstrap superuser when the connecting role is a superuser, the connecting role otherwise, or the role named by `granted_by`. `state=present` makes that grant even when another role has granted the membership, and `state=absent` and `state=exact` neither revoke nor report a grant recorded under another role. A task that was unchanged may report changed on its first run and fire its handlers. The deprecated `groups` option keeps treating the (group, target role) pair as the membership, whoever granted it (https://github.com/ansible-collections/community.postgresql/issues/757). ## Deprecated Features - postgresql_membership - the top-level `groups` option is deprecated and will be removed in `community.postgresql 6.0.0`. `granted_by_any` with the `groups` key of `memberships` behaves the same on every version; `target_roles` stays at the top level, and an empty `memberships` list with `state=exact` replaces an empty `groups` list. ## Removed Features (previously deprecated) - postgresql modules - the `login`, `host`, `unix_socket` and `port` aliases have been removed in `community.postgresql 5.0.0`. Use the `login_user`, `login_host`, `login_unix_socket` and `login_port` options instead (https://github.com/ansible-collections/community.postgresql/issues/847). - postgresql_copy - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_db - the `rename` choice of the `state` option has been removed. Use the `community.postgresql.postgresql_query` module instead (https://github.com/ansible-collections/community.postgresql/issues/833). - postgresql_ext - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_idx - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_membership - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_owner - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_pg_hba - the `keep_comments_at_rules` option has been removed. It had no effect since it was deprecated (https://github.com/ansible-collections/community.postgresql/issues/810). - postgresql_ping - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_privs - the `db` and `database` aliases of the `login_db` option have been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_publication - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_query - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_schema - the `db` and `database` aliases of the `login_db` option have been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_script - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_sequence - the `db` and `database` aliases of the `login_db` option have been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_sequence - the `rename_to` option has been removed. Use the `community.postgresql.postgresql_query` module instead (https://github.com/ansible-collections/community.postgresql/issues/833). - postgresql_set - the module has been removed. Please use the `community.postgresql.postgresql_alter_system` module instead (https://github.com/ansible-collections/community.postgresql/issues/823). - postgresql_slot - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_subscription - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_table - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_table - the `rename` option has been removed. Use the `community.postgresql.postgresql_query` module instead (https://github.com/ansible-collections/community.postgresql/issues/833). - postgresql_tablespace - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_tablespace - the `rename_to` option has been removed. Use the `community.postgresql.postgresql_query` module instead (https://github.com/ansible-collections/community.postgresql/issues/833). - postgresql_user - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). - postgresql_user_obj_stat_info - the `db` alias of the `login_db` option has been removed. Use the `login_db` option instead (https://github.com/ansible-collections/community.postgresql/issues/831). ## Bugfixes - postgresql_membership - fix `state=absent` and `state=exact` not removing a membership on PostgreSQL 16 and later when another role had granted it, and reporting a change on every run. The deprecated `groups` option now revokes every grant of the pair, one `REVOKE` per granting role, and fails naming the granting role when the connecting role lacks its privileges, where it used to succeed without revoking anything (https://github.com/ansible-collections/community.postgresql/issues/757). - postgresql_membership - fix a group named more than once being granted or revoked twice. - postgresql_membership - fix a group or role name containing a quote producing invalid SQL. - postgresql_membership - fix an empty `target_roles` list failing with a SQL syntax error; it is now a no-op. </details> --- ### Configuration :date: **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). :vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied. :recycle: **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. :no_bell: **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjM5LjI2NC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/community.postgresql-5.x:renovate/community.postgresql-5.x
git switch renovate/community.postgresql-5.x

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/community.postgresql-5.x
git switch renovate/community.postgresql-5.x
git rebase main
git switch main
git merge --ff-only renovate/community.postgresql-5.x
git switch renovate/community.postgresql-5.x
git rebase main
git switch main
git merge --no-ff renovate/community.postgresql-5.x
git switch main
git merge --squash renovate/community.postgresql-5.x
git switch main
git merge --ff-only renovate/community.postgresql-5.x
git switch main
git merge renovate/community.postgresql-5.x
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
peschmae
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
peschmae/ansible-home-borr!1019
No description provided.