Do not specify start_pushers in Synapse config

It's unnecessary when `pusher_instances` is populated.

Source: 6acb6d772a
This commit is contained in:
Slavi Pantaleev
2022-12-06 15:49:56 +02:00
parent 135bb5af3e
commit 663fe29ddb
3 changed files with 1 additions and 6 deletions

View File

@ -61,6 +61,7 @@
- {'old': 'matrix_synapse_workers_frontend_proxy_workers_metrics_range_start', 'new': '<removed in favor of generic workers - see https://github.com/matrix-org/synapse/pull/13645>'}
- {'old': 'matrix_synapse_ext_s3_storage_provider_path', 'new': 'matrix_synapse_ext_s3_storage_provider_base_path'}
- {'old': 'matrix_synapse_send_federation', 'new': '<unnecessary - Synapse relies on federation_sender_instances now>'}
- {'old': 'matrix_synapse_start_pushers', 'new': '<unnecessary - Synapse relies on pusher_instances now>'}
- name: (Deprecation) Catch and report renamed settings in matrix_synapse_configuration_extension_yaml