Don't require tenant prefixes when accessing internal databases in protcol=atlasproxy

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Our current implementation of expectPrefix requires commands targeting internal databases (admin, local, config) to prefix the databases. Atlasproxy depends on being able to run commands against these databases without prefixing, so we must relax our requirements.

              Assignee:
              [DO NOT USE] Backlog - Service Architecture
              Reporter:
              Matt Broadstone
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: