[DOCS-15372] Include Permissions Needed to Rename a Replicaset Created: 28/May/22  Updated: 30/Oct/23  Resolved: 12/Jul/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 4.2.0, 4.4.0, 5.0.0, 6.0.0
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Minor - P4
Reporter: Ronan Merrick Assignee: David Hou
Resolution: Done Votes: 0
Labels: server-docs-bug-bash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 36 weeks, 4 days ago
Epic Link: DOCSP-11702

 Description   

In our steps to rename a replica set, we include the commands to rename a replica set using system.replset.

We had a recent S1 Support Case where a customer had root and dbOwner for local but wasn't able to perform this and was under time pressure to do so. I think it would be helpful to list what permissions are needed, if you can't do this with root or dbOwner.

For instance the following role contains the necessary permissions:

db.runCommand( { createRole : "replsetRole", privileges : [ { resource : { db : "local", collection : "system.replset" }, actions:["find","update","remove"]}], roles : [] })


Generated at Thu Feb 08 08:12:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.