[SERVER-3437] Console safe mode Created: 18/Jul/11  Updated: 20/Jul/20  Resolved: 17/Jul/20

Status: Closed
Project: Core Server
Component/s: Admin, Shell
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor - P4
Reporter: Kushal Dave Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Won't Do Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-32849 Prompt before write commands with shell Open
Participants:

 Description   

Using the mongo console is scary - it's possible to accidentally issue deletes, updates, and drops. Less scary, but annoying, it's also possible to accidentally create a new collection and think you've, say, added an index on collection A when you created and indexed collection B. Although this can be solved to some extent with user permissions, it would be much easier operationally if the console just took a command line arg that prevented any of these mutations or at least required confirmation before doing so.



 Comments   
Comment by Jessica Sigafoos [ 17/Jul/20 ]

This feature is not, currently prioritized for the new shell. This need can be satisfied by defining user permissions.

Comment by Asya Kamsky [ 15/Aug/18 ]

This seems to be what Compass provides, to some extent.

 

Comment by James Wahlin [ 25/Apr/14 ]

The repairDatabase command should be added to the list of operations that could use a safety check. This operation will effectively lock up a replica set primary and make it unavailable to clients. When run against a mongos it can execute against all shard primaries.

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