Uploaded image for project: 'MongoDB Shell'
  1. MongoDB Shell
  2. MONGOSH-603

Redacted history is UX pain point

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 0.15.0
    • Affects Version/s: None
    • Component/s: CLI Module
    • Labels:
      None
    • 2
    • Needed
    • Hide

      A new config option, redactHistory, is introduced. It has three possible values:

      • keep: Retain the history as-is
      • remove: Remove lines with sensitive commands
      • remove-redact: remove + redact sensitive data from non-sensitive
        commands (e.g. email addresses)

      remove is the default. The setting can be changed via config.set('redactHistory', '<new value>').

      Show
      A new config option, redactHistory , is introduced. It has three possible values: keep : Retain the history as-is remove : Remove lines with sensitive commands remove-redact : remove + redact sensitive data from non-sensitive commands (e.g. email addresses) remove is the default. The setting can be changed via config.set('redactHistory', '<new value>') .
    • Iteration Düsseldorf

      As a user, I’m surprised when I don’t see my most recently entered command if I hit the 'up' key, and possibly hit 'Enter' on the wrong command if I’m a fast typer who’s used to other shells not redacting history entries.

      It would be great to be able to turn off the redaction feature, and/or redact only credentials but leave the actual command in the history, and/or only apply redaction for the store-to-disk part but keep the full command in memory.

            Assignee:
            anna.henningsen@mongodb.com Anna Henningsen
            Reporter:
            anna.henningsen@mongodb.com Anna Henningsen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: