postgresql modules: improve trust_input parameter's documentation, improve CI tests (#309)

* postgresql modules: improve trust_input parameter's documentation, improve CI tests

* fix CI

plugins/modules/database/postgresql/postgresql_db.py

@@ -107,7 +107,9 @@ options:
     type: str
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(owner), I(conn_limit), I(encoding),
+      I(db), I(template), I(tablespace), I(session_role) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 seealso:

plugins/modules/database/postgresql/postgresql_ext.py

@@ -82,7 +82,9 @@ options:
     type: str
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(ext), I(schema),
+      I(version), I(session_role) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 seealso:

plugins/modules/database/postgresql/postgresql_idx.py

@@ -116,7 +116,10 @@ options:
     default: no
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(idxname), I(session_role),
+      I(schema), I(table), I(columns), I(tablespace), I(storage_params),
+      I(cond) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 

plugins/modules/database/postgresql/postgresql_lang.py

@@ -73,7 +73,8 @@ options:
     description:
     - Switch to session_role after connecting.
     - The specified I(session_role) must be a role that the current I(login_user) is a member of.
-    - Permissions checking for SQL commands is carried out as though the I(session_role) were the one that had logged in originally.
+    - Permissions checking for SQL commands is carried out as though the
+      I(session_role) were the one that had logged in originally.
     type: str
   state:
     description:
@@ -106,7 +107,9 @@ options:
     type: str
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(lang), I(session_role),
+      I(owner) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 seealso:

plugins/modules/database/postgresql/postgresql_membership.py

@@ -74,7 +74,9 @@ options:
     type: str
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(groups),
+      I(target_roles), I(session_role) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 seealso:

plugins/modules/database/postgresql/postgresql_owner.py

@@ -72,7 +72,9 @@ options:
     type: str
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(new_owner), I(obj_name),
+      I(reassign_owned_by), I(session_role) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 seealso:

plugins/modules/database/postgresql/postgresql_privs.py

@@ -159,7 +159,9 @@ options:
     - ssl_rootcert
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(roles), I(target_roles), I(session_role),
+      I(schema) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 

plugins/modules/database/postgresql/postgresql_publication.py

@@ -71,7 +71,9 @@ options:
     type: str
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(name), I(tables), I(owner),
+      I(session_role), I(params) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 notes:

plugins/modules/database/postgresql/postgresql_schema.py

@@ -71,7 +71,8 @@ options:
     aliases: [ ssl_rootcert ]
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(schema), I(owner), I(session_role) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 seealso:

plugins/modules/database/postgresql/postgresql_sequence.py

@@ -137,7 +137,9 @@ options:
     - login_db
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(sequence), I(schema), I(rename_to),
+      I(owner), I(newschema), I(session_role) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 notes:

plugins/modules/database/postgresql/postgresql_subscription.py

@@ -89,7 +89,9 @@ options:
     type: str
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(name), I(publications), I(owner),
+      I(session_role), I(connparams), I(subsparams) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 

plugins/modules/database/postgresql/postgresql_tablespace.py

@@ -77,7 +77,9 @@ options:
     - login_db
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(tablespace), I(location), I(owner),
+      I(rename_to), I(session_role), I(settings_list) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 

plugins/modules/database/postgresql/postgresql_user.py

@@ -149,7 +149,9 @@ options:
     type: str
   trust_input:
     description:
-    - If C(no), check whether values of some parameters are potentially dangerous.
+    - If C(no), check whether values of parameters I(name), I(password), I(privs), I(expires),
+      I(role_attr_flags), I(groups), I(comment), I(session_role) are potentially dangerous.
+    - It makes sense to use C(yes) only when SQL injections via the parameters are possible.
     type: bool
     default: yes
 notes: