[SERVER-13395] Warn if config file value and command line value differ Created: 27/Mar/14 Updated: 06/Dec/22 Resolved: 15/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Usability |
| Affects Version/s: | 2.6.0-rc2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
If you for example set security.authentication=mandatory in the config file, but have --noauth in your command line args, the server just silently takes the command line arg, in this case --noauth as the true value of the parameter, with no indication of the conflict. We should a warning at startup if there are conflicting values between the config file and command line arguments. |
| Comments |
| Comment by Andy Schwerin [ 15/Sep/16 ] |
|
This is consistent with the behavior of many if not all *nix utilities. The command line overrides the config file, and (typically) later arguments on the command line override earlier ones. |