Make sure every config option has a name that can be used either on the command line or in the config file

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.6.0-rc2
    • Component/s: Usability
    • Server Security
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Some configuration options have different names depending on whether they're being set via the command line or via a config file. For example, security.authentication works only via the config file, while --auth and --noauth work only via the command line.
      I feel like this has the potential to confuse users who look at their production config file to figure out what options to use on their dev box, or people who look at their makeshift scripts to figure out what options to put into the config file when moving to production.

              Assignee:
              [DO NOT USE] Backlog - Security Team
              Reporter:
              Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: