Automation should handle multiple hostname aliases for each server
In order to separate replication, client and administrative traffic, servers may have multiple network interfaces using different IP and hostname aliases associated with them.
According to the requirements described on https://docs.opsmanager.mongodb.com/current/tutorial/provisioning-prep/#server-networking-access Automation currently can use only the server hostname defined as
hostname -f and cannot use any of the other aliases matching to other IP addresses for the other machine host aliases.
Please add some way to customize which host alias Automation should use as a configuration parameter for the Agent.