-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Test Infrastructure
-
Fully Compatible
-
DevProd Test Infra 2026-05-19
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This was already fixed in v7.0 and v8.0 in my big monguard backports.
Currently the behavior is
1. the mongo shell does internal logic to find the current base path
2. if the MONGO_PATH env var exists. it adds those after in the path
This is wrong because MONGO_SHELL should tell it what to parse first. This caused some issues in v7 and v8 which is how I caught this.
The new behavior is that the MONGO_PATH is used exactly how it is passed and when MONGO_PATH does not exist it uses the same logic internally to determine which directory to use.