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

---

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

- when: matrix_mautrix_telegram_service_stat.stat.exists | bool
  block:
    - name: Ensure matrix-mautrix-telegram is stopped
      ansible.builtin.service:
        name: matrix-mautrix-telegram
        state: stopped
        enabled: false
        daemon_reload: true

    - name: Ensure matrix-mautrix-telegram.service doesn't exist
      ansible.builtin.file:
        path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-telegram.service"
        state: absent
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`
More ansible-lint fixes 2022-07-18 10:22:05 +02:00			`ansible.builtin.stat:`
matrix_systemd_path -> devture_systemd_docker_base_systemd_path (via com.devture.ansible.role.systemd_docker_base) 2022-11-04 15:38:38 +01:00			`path: "{{ devture_systemd_docker_base_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`

Optimize uninstall tasks a bit - forego removing Docker images - it's not effective anyway, because it only removes the last version.. which is a drop in the bucket, usually - do not reload systemd - it's none of our business. `--tags=start`, etc., handle this - combine all uninstall tasks under a single block, which only runs if we detect traces (a leftover systemd .service file) of the component. If no such .service is detected, we skip them all. This may lead to incorect cleanup in rare cases, but is good enough for the most part. 2022-11-25 16:17:54 +01:00			`- when: matrix_mautrix_telegram_service_stat.stat.exists \| bool`
			`block:`
			`- name: Ensure matrix-mautrix-telegram is stopped`
			`ansible.builtin.service:`
			`name: matrix-mautrix-telegram`
			`state: stopped`
			`enabled: false`
			`daemon_reload: true`
Make bridge uninstallation stop services Fixes #155 (Github Issue) 2019-05-21 04:27:05 +02:00
Optimize uninstall tasks a bit - forego removing Docker images - it's not effective anyway, because it only removes the last version.. which is a drop in the bucket, usually - do not reload systemd - it's none of our business. `--tags=start`, etc., handle this - combine all uninstall tasks under a single block, which only runs if we detect traces (a leftover systemd .service file) of the component. If no such .service is detected, we skip them all. This may lead to incorect cleanup in rare cases, but is good enough for the most part. 2022-11-25 16:17:54 +01:00			`- name: Ensure matrix-mautrix-telegram.service doesn't exist`
			`ansible.builtin.file:`
			`path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-mautrix-telegram.service"`
			`state: absent`