postgresql_privs: double use of login_* arguments #406
Comments
|
@felixfontein thanks for reporting the issue! Agreed, doesn't look good. Will see what we can do with it |
|
working on it |
|
created a PR #407 please take a look |
hunleyd
pushed a commit
that referenced
this issue
Feb 3, 2023
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
May 24, 2023
7.6.0 Major Changes community.postgresql - postgresql_privs - the ``password`` argument is deprecated and will be removed in community.postgresql 4.0.0, use the ``login_password`` argument instead (ansible-collections/community.postgresql#406). infoblox.nios_modules - Added Grid Master Candidate feature - Added Member Assignment to network and ranges - Added NIOS Range module with Create, Update and Delete features - Fixes issue unable to update/delete EAs using Ansible plugin - Fixes static and dynamic allocation of IPV4 address of A Record - Fixes to Update host name of NIOS member - Updates default WAPI version to 2.9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
The module argumentspec declares multiple
login_*options as aliases of other options, while these are separate options defined in the docs fragment / module utils!This looks like a bug to me, and can cause warnings by ansible-core if someone uses both the "alias" and the real option (like
hostandlogin_host). If the intention was to 'default' these options to thelogin_*versions, this should be done by explicit code.ISSUE TYPE
COMPONENT NAME
postgresql_privs
The text was updated successfully, but these errors were encountered: