Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-75651

Exhaustively identify internal namespaces that should not be modified by user commands

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Execution NAMR Team 2023-06-26
    • 3

      Periodically a new SERVER ticket pops up where fuzz testing has messed up internal namespace state via drop/rename/etc.

      We should explore creating a new auth role/permission for internal namespaces – so that downstream products can still modify internal collections as necessary – and labeling internal namespaces such that they can be identified as such.

      Perhaps we can add a tag/field to NamespaceString for internal collection identification. And then create a list of commands (maybe via a test) that are not allowed to modify internal collections.

            Assignee:
            Unassigned Unassigned
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: