Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.

DOCSP-32849-add-reference-to-restore-role #737

Merged
merged 11 commits into from
Apr 28, 2025
6 changes: 3 additions & 3 deletions source/includes/fact-permissions-body.rst
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
The user specified in the ``mongosync`` connection string must have the
required permissions on the source and destination clusters. The
permissions vary depending on your environment and if you want to
modify write-blocking settings or use reverse sync.
required :ref:`c2c-permissions-and-roles` on the source and destination
clusters. The permissions vary depending on your environment and if you
want to modify write-blocking settings or use reverse sync.

19 changes: 13 additions & 6 deletions source/reference/api/start.txt
Original file line number Diff line number Diff line change
Expand Up @@ -141,10 +141,14 @@ Request Body Parameters
cluster while migration is in progress, and unblocks writes right
before ``canWrite`` is ``true``.

To reverse sync, the ``enableUserWriteBlocking`` field must be set
to ``"sourceAndDestination"``. To allow the source cluster
to accept writes again, for example after running migration tests,
run the following command:
.. include:: /includes/fact-permissions-body.rst

To reverse sync, the user must have assigned the :authrole:`restore`
role for both source and destination and the ``enableUserWriteBlocking``
field must be set to ``"sourceAndDestination"``.

To allow the source cluster to accept writes again, for example
after running migration tests, run the following command:

.. code-block:: shell

Expand Down Expand Up @@ -176,8 +180,11 @@ Request Body Parameters
- If set to ``true``, enables the sync operation to be
reversed.

To reverse sync, the ``enableUserWriteBlocking`` field must be set
to ``sourceAndDestination``.
.. include:: /includes/fact-permissions-body.rst

To reverse sync, the user must have assigned the :authrole:`restore`
role for both source and destination and the ``enableUserWriteBlocking``
field must be set to ``sourceAndDestination``.

This option is not supported for the following configurations:

Expand Down