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

# SPDX-FileCopyrightText: 2024 MDAD Team and contributors
#
# SPDX-License-Identifier: AGPL-3.0-or-later

---

- tags:
    - setup-all
    - setup-mautrix-telegram
    - install-all
    - install-mautrix-telegram
  block:
    - when: matrix_mautrix_telegram_enabled | bool
      ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml"

    - when: matrix_mautrix_telegram_enabled | bool
      ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml"

- tags:
    - setup-all
    - setup-mautrix-telegram
  block:
    - when: not matrix_mautrix_telegram_enabled | bool
      ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml"
Setting up REUSE: add copyright statements to yml files in roles/custom/ Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> 2024-12-07 17:34:44 +01:00			`# SPDX-FileCopyrightText: 2024 MDAD Team and contributors`
			`#`
			`# SPDX-License-Identifier: AGPL-3.0-or-later`

fix: all praise the allmighty yamllinter 2022-02-05 21:32:54 +01:00			`---`
Do not run matrix-nginx-proxy config injection tasks unless necessary These `init.yml` (now `inject_into_nginx_proxy.yml`) tasks do not need to `always` run. They only need to run for `setup-all` and `setup-nginx-proxy`. Unless we're dealing with these 2 tags, we can spare ourselves a lot of work. This patch also moves the `when` statement from `init.yml` into `main.yml` in an effort to further optimize things by potentially avoiding the extra file include. 2022-11-23 14:52:58 +01:00
Fix all 300+ ansible-lint-reported errors 2023-03-07 16:28:10 +01:00			`- tags:`
			`- setup-all`
			`- setup-mautrix-telegram`
			`- install-all`
			`- install-mautrix-telegram`
			`block:`
Replace most import_tasks calls with include_tasks for improved performance 2022-11-24 10:33:30 +01:00			`- when: matrix_mautrix_telegram_enabled \| bool`
			`ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml"`
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
Replace most import_tasks calls with include_tasks for improved performance 2022-11-24 10:33:30 +01:00			`- when: matrix_mautrix_telegram_enabled \| bool`
			`ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml"`
Fix all 300+ ansible-lint-reported errors 2023-03-07 16:28:10 +01:00
			`- tags:`
Add install-* tags for quicker runs 2022-11-25 15:02:51 +01:00			`- setup-all`
			`- setup-mautrix-telegram`
Fix all 300+ ansible-lint-reported errors 2023-03-07 16:28:10 +01:00			`block:`
Replace most import_tasks calls with include_tasks for improved performance 2022-11-24 10:33:30 +01:00			`- when: not matrix_mautrix_telegram_enabled \| bool`
			`ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml"`