After #25 and #26 were merged and deployed as version v0.1.14, I updated Vi-mongo to v0.1.14 and successfully connected to my sharded cluster.
After connecting I was greeted by a missing database pane and no databases or collections. My enterprise restricts access to some databases so queries to enumerate collections do not work, and no content is rendered in the pane even for sucessfully-queried databases.
Suggestion: when a database cannot be read because of restricted access, do not list that database in the databases list and do not attempt to enumerate collections for that database. Skip it and only render the databases whose collections can be enumerated.
Expected Behavior
I connect to my sharded cluster and see Databases listed with collections at a nested indentation level.
Great, thanks for finding another bug, I will create a PR for this one and fix it as soon as possible (especially the visibility of the password in the logs).
After #25 and #26 were merged and deployed as version v0.1.14, I updated Vi-mongo to v0.1.14 and successfully connected to my sharded cluster.
After connecting I was greeted by a missing database pane and no databases or collections. My enterprise restricts access to some databases so queries to enumerate collections do not work, and no content is rendered in the pane even for sucessfully-queried databases.
Suggestion: when a database cannot be read because of restricted access, do not list that database in the databases list and do not attempt to enumerate collections for that database. Skip it and only render the databases whose collections can be enumerated.
Expected Behavior
I connect to my sharded cluster and see Databases listed with collections at a nested indentation level.
Observed Behavior
Vi-mongo version:
TUI:
Logs:
Small security nitpick: the vi-mongo.log logfile contained my password in plaintext, can you anonymize before logging to file?