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

---

- name: Retrieve IP of postgres container
  command: "{{ matrix_host_command_docker }} inspect matrix-postgres --format='{% raw %}{{ .NetworkSettings.Networks.{% endraw %}{{ matrix_docker_network }}{% raw %}.IPAddress }}{% endraw %}'"
  register: matrix_postgres_container_ip

- name: Create additional users in postgres
  postgresql_user:
    name: "{{ item.username }}"
    password: "{{ item.pass }}"
    login_host: "{{ matrix_postgres_container_ip.stdout }}"
    login_port: 5432
    login_user: "{{ matrix_postgres_connection_username }}"
    login_password: "{{ matrix_postgres_connection_password }}"
    login_db: "{{ matrix_postgres_db_name }}"
  loop: "{{ matrix_postgres_additional_databases }}"

- name: Create additional users in postgres
  postgresql_db:
    name: "{{ item.name }}"
    owner: "{{ item.username }}"
    lc_ctype: 'C'
    lc_collate: 'C'
    login_host: "{{ matrix_postgres_container_ip.stdout }}"
    login_port: 5432
    login_user: "{{ matrix_postgres_connection_username }}"
    login_password: "{{ matrix_postgres_connection_password }}"
  loop: "{{ matrix_postgres_additional_databases }}"
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.) 4 years ago			`---`
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). 4 years ago
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.) 4 years ago			`- name: Retrieve IP of postgres container`
Determine matrix-postgres IP address without relying on jq To avoid needing to have `jq` installed on the machine, we could: - try to run jq in a Docker container using some small image providing that - better yet, avoid `jq` altogether 4 years ago			`command: "{{ matrix_host_command_docker }} inspect matrix-postgres --format='{% raw %}{{ .NetworkSettings.Networks.{% endraw %}{{ matrix_docker_network }}{% raw %}.IPAddress }}{% endraw %}'"`
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.) 4 years ago			`register: matrix_postgres_container_ip`

			`- name: Create additional users in postgres`
			`postgresql_user:`
Allow username of additional Postgres databases to be different We'll most likely use one that matches the database name, but it's better to have it configurable. 4 years ago			`name: "{{ item.username }}"`
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.) 4 years ago			`password: "{{ item.pass }}"`
			`login_host: "{{ matrix_postgres_container_ip.stdout }}"`
			`login_port: 5432`
			`login_user: "{{ matrix_postgres_connection_username }}"`
			`login_password: "{{ matrix_postgres_connection_password }}"`
			`login_db: "{{ matrix_postgres_db_name }}"`
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). 4 years ago			`loop: "{{ matrix_postgres_additional_databases }}"`
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.) 4 years ago
			`- name: Create additional users in postgres`
			`postgresql_db:`
			`name: "{{ item.name }}"`
Allow username of additional Postgres databases to be different We'll most likely use one that matches the database name, but it's better to have it configurable. 4 years ago			`owner: "{{ item.username }}"`
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.) 4 years ago			`lc_ctype: 'C'`
			`lc_collate: 'C'`
			`login_host: "{{ matrix_postgres_container_ip.stdout }}"`
			`login_port: 5432`
			`login_user: "{{ matrix_postgres_connection_username }}"`
			`login_password: "{{ matrix_postgres_connection_password }}"`
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). 4 years ago			`loop: "{{ matrix_postgres_additional_databases }}"`