瀏覽代碼

Prevent generic workers being combined with any of the other types

Until now, the validation check would only get tripped up
if generic workers are used, combined with at least one EACH
other type of specialized workers.

This means that someone doing this:

```
matrix_synapse_workers_preset: one-of-each
matrix_synapse_workers_client_reader_workers_count: 5
```

.. would not have triggered this safety check.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3100
pull/3119/head
Slavi Pantaleev 2 年之前
父節點
當前提交
3c7f896246
共有 1 個檔案被更改,包括 1 行新增1 行删除
  1. +1
    -1
      roles/custom/matrix-synapse/tasks/validate_config.yml

+ 1
- 1
roles/custom/matrix-synapse/tasks/validate_config.yml 查看文件

@@ -51,7 +51,7 @@
ansible.builtin.fail:
msg: >-
Generic workers should not be mixed with the new specialized worker types (room workers, sync workers, client readers, and federation readers)
when: matrix_synapse_workers_generic_workers_count | int > 0 and matrix_synapse_workers_room_workers_count | int > 0 and matrix_synapse_workers_sync_workers_count | int > 0 and matrix_synapse_workers_client_reader_workers_count | int > 0 and matrix_synapse_workers_federation_reader_workers_count | int > 0
when: matrix_synapse_workers_generic_workers_count | int > 0 and ((matrix_synapse_workers_room_workers_count | int + matrix_synapse_workers_sync_workers_count | int + matrix_synapse_workers_client_reader_workers_count | int + matrix_synapse_workers_federation_reader_workers_count | int) > 0)

- name: (Deprecation) Catch and report renamed settings
ansible.builtin.fail:


Loading…
取消
儲存