Sometimes users could run into "mongoctl error: Config file /Users//.mongoctl/mongoctl.config does not exist." while running basic commands after installation.
It's because setup.py found ~/.mongoctl directory was created, while not those sample config files, which could happen in some race conditions e.g. an incomplete/messy un-installation followed by another installation.
Feel it could be safer to always attempt to create sample config files, even though the ~/.mongoctl directory has been created in setup.py, not a big deal in terms of performance impact.
Sometimes users could run into "mongoctl error: Config file /Users//.mongoctl/mongoctl.config does not exist." while running basic commands after installation.
It's because setup.py found ~/.mongoctl directory was created, while not those sample config files, which could happen in some race conditions e.g. an incomplete/messy un-installation followed by another installation.
Feel it could be safer to always attempt to create sample config files, even though the ~/.mongoctl directory has been created in setup.py, not a big deal in terms of performance impact.