matrix-docker-ansible-deploy/roles/custom/matrix-base/tasks/ensure_fuse_installed.yml

---

# This is for both RedHat 7 and 8
- ansible.builtin.include_tasks: "{{ role_path }}/tasks/ensure_fuse_installed_redhat.yml"
  when: ansible_os_family == 'RedHat'

# This is for both Debian and Raspbian
- ansible.builtin.include_tasks: "{{ role_path }}/tasks/ensure_fuse_installed_debian.yml"
  when: ansible_os_family == 'Debian'

- ansible.builtin.include_tasks: "{{ role_path }}/tasks/ensure_fuse_installed_archlinux.yml"
  when: ansible_os_family == 'Archlinux'
Include ensure_openssl_installed and ensure_fuse_installed utils in a more reliable way This fixes a regression since the change done in c1c152f7acb931021acb3. When another role (say `matrix-jitsi`) included `roles/custom/matrix-base/tasks/util/ensure_openssl_installed.yml`, which then included `{{ role_path }}/tasks/util/ensure_openssl_installed_DISTRO.yml`, that `role_path` variable would end up being the parent role (`matrix-jitsi`) and not the `matrix-base` role, so we'd get a failure. An alternative solution may have been to avoid using `role_path`, but importing roles properly (like we've done in this patch) sounds like a better way. Unfortunately, `import_role` fails if `tasks_from` is something like `util/ensure_openssl_installed` (containing a `/`), so I had to move these utils out of `util/`. Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2228 2022-11-05 09:15:35 +02:00			`---`

			`# This is for both RedHat 7 and 8`
			`- ansible.builtin.include_tasks: "{{ role_path }}/tasks/ensure_fuse_installed_redhat.yml"`
			`when: ansible_os_family == 'RedHat'`

			`# This is for both Debian and Raspbian`
			`- ansible.builtin.include_tasks: "{{ role_path }}/tasks/ensure_fuse_installed_debian.yml"`
			`when: ansible_os_family == 'Debian'`

			`- ansible.builtin.include_tasks: "{{ role_path }}/tasks/ensure_fuse_installed_archlinux.yml"`
			`when: ansible_os_family == 'Archlinux'`