From bc5651b27b38bdf145c1a1eb51730670bce3aa7e Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 16 Feb 2026 05:21:35 +0900 Subject: [PATCH] Remove a task to check appservice-slack and mautrix-slack bot usernames Signed-off-by: Suguru Hirahara --- .../tasks/validate_config.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml index 0d3adfdec..c2e3019d0 100644 --- a/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml +++ b/roles/custom/matrix-bridge-mautrix-slack/tasks/validate_config.yml @@ -18,15 +18,6 @@ - {'name': 'matrix_mautrix_slack_database_hostname', when: "{{ matrix_mautrix_slack_database_engine == 'postgres' }}"} - {'name': 'matrix_mautrix_slack_container_network', when: true} -- name: Fail if appservice-slack and mautrix-slack have conflicting bot usernames - when: matrix_appservice_slack_enabled | default(False) | bool and matrix_mautrix_slack_appservice_bot_username == matrix_appservice_slack_bot_name | default ('') - ansible.builtin.fail: - msg: | - The appservice-slack and mautrix-slack components are both enabled and use the same bot username ({{ matrix_mautrix_slack_appservice_bot_username }}), as per their default configuration, which causes a conflict. - To resolve the conflict, make one of these components use a different username. - Consider either changing `matrix_mautrix_slack_appservice_bot_username` (the bot username for the mautrix-slack component) or `matrix_appservice_slack_bot_name` (the bot username for the appservice-slack component). - We recommend that you change the username for the newly-added (and yet unused) component. - - name: (Deprecation) Catch and report renamed mautrix-slack variables ansible.builtin.fail: msg: >-