[SERVER-25323] Generic way to make test-only setParameters Created: 28/Jul/16 Updated: 20/Feb/19 Resolved: 17/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Sara Golemon |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 2018-12-17 | ||||||||
| Participants: | |||||||||
| Description |
|
On several occasions our team has introduced new setParameters which are intended to be configured only for testing purposes. We do not have an obvious way to enforce, however, that a user who is allowed to run the setParameter command cannot change the parameter in a production environment. There should be a way to add setParameters that can only be changed by authorized users when the server is configured with enableTestCommands=true. This could also help our users distinguish between legitimate knobs that they might want to tune and our internal testing machinery. |
| Comments |
| Comment by Githook User [ 17/Dec/18 ] |
|
Author: {'username': 'sgolemon', 'email': 'sara.golemon@mongodb.com', 'name': 'Sara Golemon'}Message: |
| Comment by Max Hirschhorn [ 25/Sep/17 ] |
|
I think we can use a similar approach to what was taken in |