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

---

- name: Check existence of matrix-mautrix-telegram service
  stat:
    path: "{{ matrix_systemd_path }}/matrix-mautrix-telegram.service"
  register: matrix_mautrix_telegram_service_stat

- name: Ensure matrix-mautrix-telegram is stopped
  service:
    name: matrix-mautrix-telegram
    state: stopped
    enabled: no
    daemon_reload: yes
  when: "matrix_mautrix_telegram_service_stat.stat.exists"

- name: Ensure matrix-mautrix-telegram.service doesn't exist
  file:
    path: "{{ matrix_systemd_path }}/matrix-mautrix-telegram.service"
    state: absent
  when: "matrix_mautrix_telegram_service_stat.stat.exists"

- name: Ensure systemd reloaded after matrix-mautrix-telegram.service removal
  service:
    daemon_reload: yes
  when: "matrix_mautrix_telegram_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 16:47:22 +02:00			`---`

Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 04:27:05 +02:00			`- name: Check existence of matrix-mautrix-telegram service`
			`stat:`
Made directory variables for /etc/systemd/system , /etc/cron.d , /usr/local/bin 2020-03-24 19:27:58 +01:00			`path: "{{ matrix_systemd_path }}/matrix-mautrix-telegram.service"`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 04:27:05 +02:00			`register: matrix_mautrix_telegram_service_stat`

			`- name: Ensure matrix-mautrix-telegram is stopped`
			`service:`
			`name: matrix-mautrix-telegram`
			`state: stopped`
Disable systemd services when stopping to uninstall them Until now, we were leaving services "enabled" (symlinks in /etc/systemd/system/multi-user.target.wants/). We clean these up now. Broken symlinks may still exist in older installations that enabled/disabled services. We're not taking care to fix these up. It's just a cosmetic defect anyway. 2021-11-10 16:39:21 +01:00			`enabled: no`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 04:27:05 +02:00			`daemon_reload: yes`
			`when: "matrix_mautrix_telegram_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 16:47:22 +02:00			`- name: Ensure matrix-mautrix-telegram.service doesn't exist`
			`file:`
Made directory variables for /etc/systemd/system , /etc/cron.d , /usr/local/bin 2020-03-24 19:27:58 +01:00			`path: "{{ matrix_systemd_path }}/matrix-mautrix-telegram.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 16:47:22 +02:00			`state: absent`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 04:27:05 +02:00			`when: "matrix_mautrix_telegram_service_stat.stat.exists"`

			`- name: Ensure systemd reloaded after matrix-mautrix-telegram.service removal`
			`service:`
			`daemon_reload: yes`
			`when: "matrix_mautrix_telegram_service_stat.stat.exists"`