You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Description:
Currently, the /_synapse/admin/v1/shutdown_room/{room_id} admin api moves all users to a new or existing room upon calling.
It is not possible to avoid this by simply omitting the new_room_user_id parameters, as can be done when using the /_synapse/admin/v1/rooms/<room_id>/delete endpoint.
Since the underlying code (RoomShutdownHandler) already supports the omission of new_room_user_id I think it is sufficient to just remove the restrictions currently in place and update the documentation to fix my issue.
The text was updated successfully, but these errors were encountered:
/debug does not work for me probably due to bug in either synapse or my configuration. I looked for alternatives and found the /shutdown endpoint and noticed the discrepancy between their parameters.
If it is intended to drop the /shutdown endpoint then please close this issue.
Description:
Currently, the
/_synapse/admin/v1/shutdown_room/{room_id}
admin api moves all users to a new or existing room upon calling.It is not possible to avoid this by simply omitting the
new_room_user_id
parameters, as can be done when using the/_synapse/admin/v1/rooms/<room_id>/delete
endpoint.Since the underlying code (
RoomShutdownHandler
) already supports the omission ofnew_room_user_id
I think it is sufficient to just remove the restrictions currently in place and update the documentation to fix my issue.The text was updated successfully, but these errors were encountered: