matrix-docker-ansible-deploy/roles/matrix-base/tasks/self_check_dns.yml

---

- set_fact:
    dns_srv_record_checks: []

- block:
    - set_fact:
        dns_srv_record_check_ma1sd:
          service_and_protocol: "_matrix-identity._tcp"
          domain: "{{ (matrix_domain + '.') }}"
          expected_target: "{{ (matrix_server_fqn_matrix + '.') }}"
          expected_port: 443

    - name: Determine domains that we require certificates for (ma1sd)
      set_fact:
        dns_srv_record_checks: "{{ dns_srv_record_checks + [dns_srv_record_check_ma1sd] }}"
  when: matrix_ma1sd_enabled|bool

- name: Perform DNS SRV checks
  include_tasks: "{{ role_path }}/tasks/self_check_dns_srv.yml"
  with_items: "{{ dns_srv_record_checks }}"
  loop_control:
    loop_var: dns_srv_record_check
Add self-check command 2018-10-21 17:58:25 +08:00			`---`

Do not ask for _matrix._tcp SRV records anymore With most people on Synapse v0.99+ and Synapse v1.0 now available, we should no longer try to be backward compatible with Synapse 0.34, because this just complicates the instructions for no good reason. 2019-06-12 19:51:10 +08:00			`- set_fact:`
			`dns_srv_record_checks: []`
Add self-check command 2018-10-21 17:58:25 +08:00
Check DNS SRV record for _matrix-identity._tcp when mxisd enabled 2019-01-08 16:39:22 +08:00			`- block:`
			`- set_fact:`
Rename variables (s/mxisd/ma1sd/) and adapt roles 2020-01-09 05:31:44 +08:00			`dns_srv_record_check_ma1sd:`
Check DNS SRV record for _matrix-identity._tcp when mxisd enabled 2019-01-08 16:39:22 +08:00			`service_and_protocol: "_matrix-identity._tcp"`
Rename some variables 2019-02-28 17:51:09 +08:00			`domain: "{{ (matrix_domain + '.') }}"`
			`expected_target: "{{ (matrix_server_fqn_matrix + '.') }}"`
Check DNS SRV record for _matrix-identity._tcp when mxisd enabled 2019-01-08 16:39:22 +08:00			`expected_port: 443`
Add self-check command 2018-10-21 17:58:25 +08:00
Rename variables (s/mxisd/ma1sd/) and adapt roles 2020-01-09 05:31:44 +08:00			`- name: Determine domains that we require certificates for (ma1sd)`
Check DNS SRV record for _matrix-identity._tcp when mxisd enabled 2019-01-08 16:39:22 +08:00			`set_fact:`
Rename variables (s/mxisd/ma1sd/) and adapt roles 2020-01-09 05:31:44 +08:00			`dns_srv_record_checks: "{{ dns_srv_record_checks + [dns_srv_record_check_ma1sd] }}"`
			`when: matrix_ma1sd_enabled\|bool`
Add self-check command 2018-10-21 17:58:25 +08:00
Check DNS SRV record for _matrix-identity._tcp when mxisd enabled 2019-01-08 16:39:22 +08:00			`- name: Perform DNS SRV checks`
Split playbook into multiple roles As suggested in #63 (Github issue), splitting the playbook's logic into multiple roles will be beneficial for maintainability. This patch realizes this split. Still, some components affect others, so the roles are not really independent of one another. For example: - disabling mxisd (`matrix_mxisd_enabled: false`), causes Synapse and riot-web to reconfigure themselves with other (public) Identity servers. - enabling matrix-corporal (`matrix_corporal_enabled: true`) affects how reverse-proxying (by `matrix-nginx-proxy`) is done, in order to put matrix-corporal's gateway server in front of Synapse We may be able to move away from such dependencies in the future, at the expense of a more complicated manual configuration, but it's probably not worth sacrificing the convenience we have now. As part of this work, the way we do "start components" has been redone now to use a loop, as suggested in #65 (Github issue). This should make restarting faster and more reliable. 2019-01-12 23:53:00 +08:00			`include_tasks: "{{ role_path }}/tasks/self_check_dns_srv.yml"`
Check DNS SRV record for _matrix-identity._tcp when mxisd enabled 2019-01-08 16:39:22 +08:00			`with_items: "{{ dns_srv_record_checks }}"`
			`loop_control:`
Rename some variables 2019-02-28 17:51:09 +08:00			`loop_var: dns_srv_record_check`