matrix-docker-ansible-deploy/roles/matrix-bridge-mautrix-whatsapp/tasks/init.yml

- set_fact:
    matrix_systemd_services_list: "{{ matrix_systemd_services_list + ['matrix-mautrix-whatsapp'] }}"
  when: matrix_mautrix_whatsapp_enabled|bool

# If the matrix-synapse role is not used, these variables may not exist.
- set_fact:
    matrix_synapse_container_extra_arguments: >
      {{ matrix_synapse_container_extra_arguments|default([]) }}
      +
      {{ ["--mount type=bind,src={{ matrix_mautrix_whatsapp_base_path }}/registration.yaml,dst=/matrix-mautrix-whatsapp-registration.yaml,ro"] }}

    matrix_synapse_app_service_config_files: >
      {{ matrix_synapse_app_service_config_files|default([]) }}
      +
      {{ ["/matrix-mautrix-whatsapp-registration.yaml"] }}
  when: matrix_mautrix_whatsapp_enabled|bool
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 15:53:00 +00:00			`- set_fact:`
			`matrix_systemd_services_list: "{{ matrix_systemd_services_list + ['matrix-mautrix-whatsapp'] }}"`
Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8 2019-05-21 15:25:59 +00:00			`when: matrix_mautrix_whatsapp_enabled\|bool`
Make running --tags=setup-synapse only not fail to register bridges Until now, if `--tags=setup-synapse` was used, bridge tasks would not run and bridges would fail to register with the `matrix-synapse` role. This means that Synapse's configuration would be generated with an empty list of appservices (`app_service_config_files: []`). .. and then bridges would fail, because Synapse would not be aware of there being any bridges. From now on, bridges always run their init tasks and always register with Synapse. For the Telegram bridge, the same applies to registering with matrix-nginx-proxy. Previously, running `--tags=setup-nginx-proxy` would get rid of the Telegram endpoint configuration for the same reason. Not anymore. 2019-06-14 07:19:52 +00:00
			`# If the matrix-synapse role is not used, these variables may not exist.`
			`- set_fact:`
			`matrix_synapse_container_extra_arguments: >`
			`{{ matrix_synapse_container_extra_arguments\|default([]) }}`
			`+`
			`{{ ["--mount type=bind,src={{ matrix_mautrix_whatsapp_base_path }}/registration.yaml,dst=/matrix-mautrix-whatsapp-registration.yaml,ro"] }}`

			`matrix_synapse_app_service_config_files: >`
			`{{ matrix_synapse_app_service_config_files\|default([]) }}`
			`+`
			`{{ ["/matrix-mautrix-whatsapp-registration.yaml"] }}`
			`when: matrix_mautrix_whatsapp_enabled\|bool`