matrix-docker-ansible-deploy/roles/matrix-synapse/tasks/self_check_client_api.yml

---

- name: Check Matrix Client API
  uri:
    url: "{{ matrix_synapse_client_api_url_endpoint_public }}"
    follow_redirects: none
    validate_certs: "{{ matrix_synapse_self_check_validate_certificates }}"
  register: result_matrix_synapse_client_api
  ignore_errors: true
  check_mode: false
  when: matrix_synapse_enabled|bool

- name: Fail if Matrix Client API not working
  fail:
    msg: "Failed checking Matrix Client API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_client_api_url_endpoint_public }}`). Is Synapse running? Is port 443 open in your firewall? Full error: {{ result_matrix_synapse_client_api }}"
  when: "matrix_synapse_enabled|bool and (result_matrix_synapse_client_api.failed or 'json' not in result_matrix_synapse_client_api)"

- name: Report working Matrix Client API
  debug:
    msg: "The Matrix Client API at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_client_api_url_endpoint_public }}`) is working"
  when: matrix_synapse_enabled|bool
Add self-check command 2018-10-21 11:58:25 +02:00			`---`

			`- name: Check Matrix Client API`
			`uri:`
Make roles more independent of one another With this change, the following roles are now only dependent on the minimal `matrix-base` role: - `matrix-corporal` - `matrix-coturn` - `matrix-mailer` - `matrix-mxisd` - `matrix-postgres` - `matrix-riot-web` - `matrix-synapse` The `matrix-nginx-proxy` role still does too much and remains dependent on the others. Wiring up the various (now-independent) roles happens via a glue variables file (`group_vars/matrix-servers`). It's triggered for all hosts in the `matrix-servers` group. According to Ansible's rules of priority, we have the following chain of inclusion/overriding now: - role defaults (mostly empty or good for independent usage) - playbook glue variables (`group_vars/matrix-servers`) - inventory host variables (`inventory/host_vars/matrix.<your-domain>`) All roles default to enabling their main component (e.g. `matrix_mxisd_enabled: true`, `matrix_riot_web_enabled: true`). Reasoning: if a role is included in a playbook (especially separately, in another playbook), it should "work" by default. Our playbook disables some of those if they are not generally useful (e.g. `matrix_corporal_enabled: false`). 2019-01-16 18:05:48 +02:00			`url: "{{ matrix_synapse_client_api_url_endpoint_public }}"`
uri.follow_redirects is now a string field 2020-01-22 23:33:20 +02:00			`follow_redirects: none`
Make self-check not validate self-signed certificates By default, `--tags=self-check` no longer validates certificates when `matrix_ssl_retrieval_method` is set to `self-signed`. Besides this default, people can also enable/disable validation using the individual role variables manually. Fixes #124 (Github Issue) 2019-03-22 09:39:17 +02:00			`validate_certs: "{{ matrix_synapse_self_check_validate_certificates }}"`
Make roles more independent of one another With this change, the following roles are now only dependent on the minimal `matrix-base` role: - `matrix-corporal` - `matrix-coturn` - `matrix-mailer` - `matrix-mxisd` - `matrix-postgres` - `matrix-riot-web` - `matrix-synapse` The `matrix-nginx-proxy` role still does too much and remains dependent on the others. Wiring up the various (now-independent) roles happens via a glue variables file (`group_vars/matrix-servers`). It's triggered for all hosts in the `matrix-servers` group. According to Ansible's rules of priority, we have the following chain of inclusion/overriding now: - role defaults (mostly empty or good for independent usage) - playbook glue variables (`group_vars/matrix-servers`) - inventory host variables (`inventory/host_vars/matrix.<your-domain>`) All roles default to enabling their main component (e.g. `matrix_mxisd_enabled: true`, `matrix_riot_web_enabled: true`). Reasoning: if a role is included in a playbook (especially separately, in another playbook), it should "work" by default. Our playbook disables some of those if they are not generally useful (e.g. `matrix_corporal_enabled: false`). 2019-01-16 18:05:48 +02:00			`register: result_matrix_synapse_client_api`
Add self-check command 2018-10-21 11:58:25 +02:00			`ignore_errors: true`
fix: all praise the allmighty yamllinter 2022-02-05 22:32:54 +02:00			`check_mode: false`
Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8 2019-05-21 17:25:59 +02:00			`when: matrix_synapse_enabled\|bool`
Add self-check command 2018-10-21 11:58:25 +02:00
			`- name: Fail if Matrix Client API not working`
			`fail:`
Rename some variables 2019-02-28 11:51:09 +02:00			msg: "Failed checking Matrix Client API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_client_api_url_endpoint_public }}`). Is Synapse running? Is port 443 open in your firewall? Full error: {{ result_matrix_synapse_client_api }}"
Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8 2019-05-21 17:25:59 +02:00			`when: "matrix_synapse_enabled\|bool and (result_matrix_synapse_client_api.failed or 'json' not in result_matrix_synapse_client_api)"`
Add self-check command 2018-10-21 11:58:25 +02:00
			`- name: Report working Matrix Client API`
			`debug:`
Rename some variables 2019-02-28 11:51:09 +02:00			msg: "The Matrix Client API at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_client_api_url_endpoint_public }}`) is working"
Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8 2019-05-21 17:25:59 +02:00			`when: matrix_synapse_enabled\|bool`