ansible/test/integration/targets/postgresql/defaults/main.yml

---
# defaults file for test_postgresql_db
db_name: 'ansible_db'
db_user1: 'ansible_db_user1'
db_user2: 'ansible_db_user2'
db_user3: 'ansible_db_user3'

tmp_dir: '/tmp'
db_session_role1: 'session_role1'
db_session_role2: 'session_role2'
New integration tests for postgresql 2014-12-02 03:57:40 +01:00			`---`
			`# defaults file for test_postgresql_db`
			`db_name: 'ansible_db'`
			`db_user1: 'ansible_db_user1'`
			`db_user2: 'ansible_db_user2'`
add a intg test for issue #19835 (#21487) (postgresql_user changing role_attr_flags with no_password_checks fails) 2017-02-15 21:28:29 +01:00			`db_user3: 'ansible_db_user3'`
New integration tests for postgresql 2014-12-02 03:57:40 +01:00
			`tmp_dir: '/tmp'`
Add session_role to postgresql modules (#43650) * Allow session_role to be set for PostgreSQL By implementing session_role it becomes possible to run the specific PostgreSQL commands as a different role. The usecase that is immediately served by this, is the one that one ansible playbook can be shared by multiple users, which all have their own PostgreSQL login_user. They do not need to share login credentials, as they can share the role within the PostgreSQL database. The following example may give some insight: $ psql -U jdoe -X -d postgres postgres=> CREATE DATABASE abc; ERROR: permission denied to create database postgres=> set role postgres; SET postgres=# CREATE DATABASE abc; CREATE DATABASE fixes #43592 * Tests for session_role in PostgreSQL * Bump version_added for session_role feature * Remove explicit encrypted parameter from tests 2019-02-02 20:12:14 +01:00			`db_session_role1: 'session_role1'`
			`db_session_role2: 'session_role2'`