Fix connect_params being ignored on postgresql_privs

[JohnAtOlo]

SUMMARY

Fixes #450
Where connect_params were ignored for community.postgresql.postgresql_privs

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

postgresql_privs

ADDITIONAL INFORMATION

Previous connect_params were ignored. A helper method used in postgresql_user took care of this and other checking which was being done here, including unix socket check.

The end result is connect_params being properly honored now.

connect_params with:

    connect_params:
      sslcert: "{{ db_cert }}"
      sslkey: "{{ db_key }}"
      sslrootcert: "{{ db_ca }}"

Before: (fails with cert error, same cert error I get if I leave out connect_params entirely)

failed: [foo -> 127.0.0.1] (item={'privs': 'ALL', 'objs': 'tables', 'type': 'default_privs'}) => {"ansible_loop_var": "privilege", "changed": false, "msg": "Could not connect to database: connection to server at \"<redacted>\" (<redacted>), port 443 failed: SSL error: sslv3 alert bad certificate\n", "privilege": {"objs": "tables", "privs": "ALL", "type": "default_privs"}}

After: (uses the connect_params successfuly, like community.postgresql.postgresql_membership and community.postgresql.postgresql_user do)

ok: [foo -> 127.0.0.1] => (item={'privs': 'ALL', 'objs': 'tables', 'type': 'default_privs'})

[Andersson007]

LGTM

[Andersson007]

@JohnAtOlo thanks for the contribution!
@hunleyd thanks for reviewing!

Our bot failed to backport the patch to stable-1 as there are conflicts.
@JohnAtOlo would you like to manually backport it to stable-1? Here's the guide (use main instead of devel).
If no time, let us know.

[JohnAtOlo]

@Andersson007 the link you have there isn't loading for me.

[Andersson007]

@JohnAtOlo Oh, sorry, copy-pasted something wrong, here it is https://docs.ansible.com/ansible/devel/community/development_process.html#backporting-merged-prs-in-ansible-core

[JohnAtOlo]

Backport PR up at #455 @Andersson007