-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:OS:
node.js / npm versions:
Additional info:
-
Developer Tools
-
1
-
Not Needed
-
Iteration Zephyrosaurus
Problem Statement/Rationale
Even though mongosh does not enable telemetry if `forceDisableTelemetry` is set to true in the config file, when users run enableTelemetry() or config.set("enableTelemetry",true), mongosh tells the users telemetry is enabled (even though it isn't). Users should instead receive an error telling them to first turn off forceDisableTelemetry in order to call either of these functions else the telemetry will remain disabled.
Steps to Reproduce
- Set forceDisableTelemetry to true in mongosh config file
- Run enableTelemetry() or config.set("enableTelemetry",true) in mongosh
- See the success message
Expected Results
mongosh throws an error.
Additional Notes
Any additional information that may be useful to include.
- causes
-
MONGOSH-1769 Avoid throwing exceptions from enableTelemetry()/disableTelemetry()
- Closed