Skip to content

(DOCS-11010): Update mongorestore grants. #3332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 7, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions source/includes/access-mongorestore-collections.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,15 @@ access to restore any database if the backup data does not include

.. include:: /includes/fact-restore-role-system.profile.rst

If running :binary:`~bin.mongorestore` with :option:`--oplogReplay <mongorestore --oplogReplay>`, the
:authrole:`restore` role is insufficient to replay the oplog. To replay
the oplog, create a :ref:`user-defined role <create-user-defined-role>`
that has :authaction:`anyAction` on :ref:`resource-anyresource` and
grant only to users who must run :binary:`~bin.mongorestore` with
As of MongoDB 3.2.11, you can run :binary:`~bin.mongorestore` with
:option:`--oplogReplay <mongorestore --oplogReplay>` if you have the
:authrole:`restore` role. To replay the oplog on versions of MongoDB
3.2.10 and earlier, you must create a
:ref:`user-defined role <create-user-defined-role>` that has
:authaction:`anyAction` on :ref:`resource-anyresource` and grant only
to users who must run :binary:`~bin.mongorestore` with
:option:`--oplogReplay <mongorestore --oplogReplay>`.


.. COMMENT per the following commit, choosing the anyAction/anyResource
over the __system role.
https://github.com/mongodb/docs/commit/237c44cd3b6e4b7dbe0c9077b7571c8b7ec5d7a5