[SERVER-13396] Make sure every config option has a name that can be used either on the command line or in the config file Created: 27/Mar/14  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Usability
Affects Version/s: 2.6.0-rc2
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Security Team
Resolution: Unresolved Votes: 0
Labels: platforms-re-triaged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Security
Participants:

 Description   

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.


Generated at Thu Feb 08 03:31:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.