Repository navigation
No port causes an exception when using codepack.interfaces.MongoDB #111
Description
Hi. Thank you for the release to fix the issue raised yesterday.
I found an issue that no port key in config file causes an exception when using MongoDB interfaces in codepack, though there are specified ports in host value.
So, this config makes an error...
[mongodb]
host = host1.server:27017, host2.server:27017, host3.server:27017
If those hosts have different port numbers, there is no way to specify ports.
Activity
ihnokim commentedon May 24, 2022
Hello, I appreciate you opening another issue!
The
portshould be provided. If the ports of the three hosts are the same, you can just move the port information intoportfor a workaround.For example,
However, as you mentioned, using different ports is not supported yet. It is clearly the limit of the
interfaces, so in the near future, the "only host connection" feature will be implemented considering your feedback!p.s. I just invited you as a collaborator of this repo. Feel free to get more powerful permissions!