QEDeDandSlavi Pantaleev 56a51d8b8c matrix-synapse: keep generic worker endpoint order stable across runs ...

`matrix_synapse_workers_generic_worker_client_server_endpoints` and
`matrix_synapse_workers_generic_worker_federation_endpoints` dropped the
non-matching entries with `difference([none])`. ansible-core implements
`difference` as `list(set(a) - set(b))`, so the result follows Python's
per-process string hash seed and comes out in a different order on every
run.

The reverse-proxy companion renders these lists as nginx `location`
blocks, so its `conf.d/matrix-synapse-reverse-proxy-companion.conf`
changed, and the companion restarted, on every run, even with nothing
else to change.

`reject('none')` drops the same entries and keeps the order of
`matrix_synapse_workers_generic_worker_endpoints`. All these locations
point to the same upstream, so routing is unchanged.

2026-10-19 09:11:18 +03:00

..

main.yml

matrix-synapse: keep generic worker endpoint order stable across runs

2026-10-19 09:11:18 +03:00