Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13220

Investigate changes in SERVER-44320: Allow zoned sharding commands to be authorized via actiontypes

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.2, 4.0.14, 4.3.2, 3.6.16
    • Component/s: manual, Server
    • Labels:
      None

      Description

      Description

      Downstream Change Summary

      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.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 11 weeks, 1 day ago
                Date of 1st Reply: