define postgresql_privs due to priv deprecated in postgresql_user module | Zabbix Proxy #1215
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmayabi
changed the title
|
Seems related to #928 |
|
@mmayabi check your tests....they are failing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
When installing Zabbix Proxy with PostgreSQL, due to the deprecation of the "priv" parameter in the "community.postgresql.postgresql_user" module, the required permissions for "zabbix_proxy" are not defined. As a result, the schema import to the database is not performed.
For this reason, the "priv" parameter has been removed, and a new task is defined using the "community.postgresql.postgresql_privs" module.
ISSUE TYPE
COMPONENT NAME
PostgreSQL | GRANT ALL PRIVILEGES ON SCHEMA public TO zabbix_proxy user
ADDITIONAL INFORMATION
Tested on PostgreSQL 15.5 (Delegated)