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

---

- name: Check existence of matrix-mautrix-whatsapp service
  ansible.builtin.stat:
    path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-whatsapp.service"
  register: matrix_mautrix_whatsapp_service_stat

- name: Ensure matrix-mautrix-whatsapp is stopped
  ansible.builtin.service:
    name: matrix-mautrix-whatsapp
    state: stopped
    enabled: false
    daemon_reload: true
  when: "matrix_mautrix_whatsapp_service_stat.stat.exists"

- name: Ensure matrix-mautrix-whatsapp.service doesn't exist
  ansible.builtin.file:
    path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-whatsapp.service"
    state: absent
  when: "matrix_mautrix_whatsapp_service_stat.stat.exists"

- name: Ensure systemd reloaded after matrix-mautrix-whatsapp.service removal
  ansible.builtin.service:
    daemon_reload: true
  when: "matrix_mautrix_whatsapp_service_stat.stat.exists"
Move mautrix telegram and whatsapp into separate roles The goal is to move each bridge into its own separate role. This commit starts off the work on this with 2 bridges: - mautrix-telegram - mautrix-whatsapp Each bridge's role (including these 2) is meant to: - depend only on the matrix-base role - integrate nicely with the matrix-synapse role (if available) - integrate nicely with the matrix-nginx-proxy role (if available and if required). mautrix-telegram bridge benefits from integrating with it. - not break if matrix-synapse or matrix-nginx-proxy are not used at all This has been provoked by #174 (Github Issue). 2019-05-14 14:47:22 +00:00			`---`

Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 02:27:05 +00:00			`- name: Check existence of matrix-mautrix-whatsapp service`
More ansible-lint fixes 2022-07-18 08:22:05 +00:00			`ansible.builtin.stat:`
matrix_systemd_path -> devture_systemd_docker_base_systemd_path (via com.devture.ansible.role.systemd_docker_base) 2022-11-04 14:38:38 +00:00			`path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-whatsapp.service"`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 02:27:05 +00:00			`register: matrix_mautrix_whatsapp_service_stat`

			`- name: Ensure matrix-mautrix-whatsapp is stopped`
Use fully-qualified module names for builtin Ansible modules Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939 2022-07-18 07:39:08 +00:00			`ansible.builtin.service:`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 02:27:05 +00:00			`name: matrix-mautrix-whatsapp`
			`state: stopped`
fix: all praise the allmighty yamllinter 2022-02-05 20:32:54 +00:00			`enabled: false`
			`daemon_reload: true`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 02:27:05 +00:00			`when: "matrix_mautrix_whatsapp_service_stat.stat.exists"`

Move mautrix telegram and whatsapp into separate roles The goal is to move each bridge into its own separate role. This commit starts off the work on this with 2 bridges: - mautrix-telegram - mautrix-whatsapp Each bridge's role (including these 2) is meant to: - depend only on the matrix-base role - integrate nicely with the matrix-synapse role (if available) - integrate nicely with the matrix-nginx-proxy role (if available and if required). mautrix-telegram bridge benefits from integrating with it. - not break if matrix-synapse or matrix-nginx-proxy are not used at all This has been provoked by #174 (Github Issue). 2019-05-14 14:47:22 +00:00			`- name: Ensure matrix-mautrix-whatsapp.service doesn't exist`
Use fully-qualified module names for builtin Ansible modules Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939 2022-07-18 07:39:08 +00:00			`ansible.builtin.file:`
matrix_systemd_path -> devture_systemd_docker_base_systemd_path (via com.devture.ansible.role.systemd_docker_base) 2022-11-04 14:38:38 +00:00			`path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-whatsapp.service"`
Move mautrix telegram and whatsapp into separate roles The goal is to move each bridge into its own separate role. This commit starts off the work on this with 2 bridges: - mautrix-telegram - mautrix-whatsapp Each bridge's role (including these 2) is meant to: - depend only on the matrix-base role - integrate nicely with the matrix-synapse role (if available) - integrate nicely with the matrix-nginx-proxy role (if available and if required). mautrix-telegram bridge benefits from integrating with it. - not break if matrix-synapse or matrix-nginx-proxy are not used at all This has been provoked by #174 (Github Issue). 2019-05-14 14:47:22 +00:00			`state: absent`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 02:27:05 +00:00			`when: "matrix_mautrix_whatsapp_service_stat.stat.exists"`

			`- name: Ensure systemd reloaded after matrix-mautrix-whatsapp.service removal`
Use fully-qualified module names for builtin Ansible modules Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939 2022-07-18 07:39:08 +00:00			`ansible.builtin.service:`
fix: all praise the allmighty yamllinter 2022-02-05 20:32:54 +00:00			`daemon_reload: true`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 02:27:05 +00:00			`when: "matrix_mautrix_whatsapp_service_stat.stat.exists"`