Mark `removeUser` for deprecation

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a... driver developer
      I want... to remove unused code paths
      So that... I can reduce the complexity of the API surface we support

      User Experience

      • theĀ removeUser function, its corresponding options and tests, are deprecated and ready for removal at the next major version.

      Dependencies

      • none

      Risks/Unknowns

      • confirm the non-use of removeUser internally

      Acceptance Criteria

      Implementation Requirements

      • none

      Testing Requirements

      • none

      Documentation Requirements

      • removeUser, if mentioned publicly, should be marked as deprecated

      Follow Up Requirements

      • Later, at the next major version, remove removeUser
      • Later, at the next major version, remove dbName and authdb variables from CommandOperation.

            Assignee:
            Sean Milligan
            Reporter:
            Sean Milligan
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: