Documentation changes probably not ACTUALLY needed, but it's worth pointing out that as an implementation detail, setting `net.bindIp: *` will now result in the same behavior as `net.bindIpAll: true`. Additionally, the unexpected behavior resulting in this ticket will no longer occur. That is, CLI values for address binding will override YAML values, regardless of whether they are in the same setting or not.
I have a config file where I have set:
But if I then run;
/mongod --config /etc//mongod.conf --bind_ip 127.0.0.1
And check it with netstat -alpn, I can see that mongod is still listening on all IPs.