-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
Docs: Permissions for the addShardToZone, removeShardFromZone, and updateZoneKeyRange commands continue to permitted for use if the client possesses rights to alter the relevant system collections directly. This change allows, as an alternative, performing these actions with just the "enableSharding" action type only.
Cloud: This was an ask from Atlas.
Description of Linked Ticket
The following zoned sharding commands are currently authorized by validating whether the authenticated client is authorized to manipulate internal sharding catalog collections:
addShardToZone updateZoneKeyRange removeShardFromZone
They would be much more convenient to use if they were able to be used with specific actiontypes, like how shardCollection works.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- documents
-
SERVER-44320 Allow zoned sharding commands to be authorized via actiontypes
- Closed