pub-solar/matrix-docker-ansible-deploy
5
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
matrix-docker-ansible-deploy/roles/matrix-bridge-mautrix-whatsapp/tasks/main.yml

23 lines
664 B
YAML
Raw Normal View History

fix: all praise the allmighty yamllinter
2022-02-05 20:32:54 +00:00
---
More ansible-lint fixes
2022-07-18 08:22:05 +00:00
- ansible.builtin.import_tasks: "{{ role_path }}/tasks/init.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 14:47:22 +00:00
tags:
- always
More ansible-lint fixes
2022-07-18 08:22:05 +00:00
- ansible.builtin.import_tasks: "{{ role_path }}/tasks/validate_config.yml"
when: "run_setup | bool and matrix_mautrix_whatsapp_enabled | bool"
Make WhatsApp bridge configuration playbook-managed - following spantaleev transition of the telegram brigde - adding a validate_config task
2019-06-23 22:16:04 +00:00
tags:
- setup-all
- setup-mautrix-whatsapp
More ansible-lint fixes
2022-07-18 08:22:05 +00:00
- ansible.builtin.import_tasks: "{{ role_path }}/tasks/setup_install.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 14:47:22 +00:00
when: "run_setup and matrix_mautrix_whatsapp_enabled"
tags:
- setup-all
- setup-mautrix-whatsapp
More ansible-lint fixes
2022-07-18 08:22:05 +00:00
- ansible.builtin.import_tasks: "{{ role_path }}/tasks/setup_uninstall.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 14:47:22 +00:00
when: "run_setup and not matrix_mautrix_whatsapp_enabled"
tags:
- setup-all
- setup-mautrix-whatsapp
Reference in a new issue Copy permalink