env_aws fingerprinter should not override manually set network_interface

[schmichael]

A user ran into an issue where they were manually setting a network_interface but it was getting overwritten by the env_aws fingerprinter because they were in AWS.

We should not overwrite explicit user network configuration.

[gorset]

I'm also seeing this problem with nomad 0.8.6.

We are running most of our nodes on dedicated hardware with a few nodes in aws, using wireguard for networking. Setting network_interface to wg0 has no effect on the aws nodes, which means that nomad will register services in consul using the aws address.

Is there a good workaround that doesn't involve iptables/ip routing magic, or manual consul registration of the service (in other words, don't use nomad's consul integration for services)?

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.