matrix-docker-ansible-deploy/roles/matrix-postgres/tasks/util/create_additional_databases.yml

---

- name: Ensure matrix-postgres is started
  service:
    name: matrix-postgres
    state: started
    daemon_reload: yes
  register: matrix_postgres_service_start_result

- name: Wait a bit, so that Postgres can start
  wait_for:
    timeout: "{{ matrix_postgres_additional_databases_postgres_start_wait_timeout_seconds }}"
  delegate_to: 127.0.0.1
  become: false
  when: "matrix_postgres_service_start_result.changed|bool"

- name: Create additional Postgres user and database
  include_tasks: "{{ role_path }}/tasks/util/create_additional_database.yml"
  with_items: "{{ matrix_postgres_additional_databases }}"
  loop_control:
    loop_var: additional_db
  # Suppress logging to avoid dumping the credentials to the shell
  no_log: true
Relocate Postgres additional database creation logic Moving it above the "uninstalling" set of tasks is better. Extracting it out to another file at the same time, for readability, especially given that it will probably have to become more complex in the future (potentially installing `jq`, etc.) 2020-12-13 19:40:32 +00:00			`---`
Prevent weird loop error > Invalid data passed to 'loop', it requires a list, got this instead: matrix_postgres_additional_databases. Hint: If you passed a list/dict of just one element, try adding wantlist=True to your lookup invocation or use q/query instead of lookup. Well, or working around it, as I've done in this commit (which seems more sane than `wantlist=True` stuff). 2020-12-13 20:56:56 +00:00
Ensure matrix-postgres.service is started before creating additional users/databases 2020-12-13 22:59:59 +00:00			`- name: Ensure matrix-postgres is started`
			`service:`
			`name: matrix-postgres`
			`state: started`
			`daemon_reload: yes`
			`register: matrix_postgres_service_start_result`
Relocate Postgres additional database creation logic Moving it above the "uninstalling" set of tasks is better. Extracting it out to another file at the same time, for readability, especially given that it will probably have to become more complex in the future (potentially installing `jq`, etc.) 2020-12-13 19:40:32 +00:00
Ensure matrix-postgres.service is started before creating additional users/databases 2020-12-13 22:59:59 +00:00			`- name: Wait a bit, so that Postgres can start`
			`wait_for:`
			`timeout: "{{ matrix_postgres_additional_databases_postgres_start_wait_timeout_seconds }}"`
			`delegate_to: 127.0.0.1`
			`become: false`
			`when: "matrix_postgres_service_start_result.changed\|bool"`

			`- name: Create additional Postgres user and database`
Do not use the postgresql_user/postgresql_db modules While these modules are really nice and helpful, we can't use them for at least 2 reasons: - for us, Postgres runs in a container on a private Docker network (`--network=matrix`) without usually being exposed to the host. These modules execute on the host so they won't be able to reach it. - these modules require `psycopg2`, so we need to install it before using it. This might or might not be its own can of worms. 2020-12-13 22:25:13 +00:00			`include_tasks: "{{ role_path }}/tasks/util/create_additional_database.yml"`
			`with_items: "{{ matrix_postgres_additional_databases }}"`
			`loop_control:`
			`loop_var: additional_db`
			`# Suppress logging to avoid dumping the credentials to the shell`
			`no_log: true`