Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Some providers support http_interface in addition to the other http_ options. This is desirable functionality.

Use Case(s)

Packer is being run on disparate machines with multiple non-loopback interfaces that do not have static IPs, making use of http_bind_address cumbersome.

In particular this would be useful for users running packer on a machine that is sometimes on-prem and connected directly to the corporate network, and at other times is off-prem and connecting with a VPN tunnel.

Using http_bind_address as a workaround does work, but it's more cumbersome to look up your dynamic address each time than to simply enter the easy to remember name of the appropriate interface.

Potential configuration

As in existing plugins that support the feature

http_interface = "vmx0" // or tun0, eth0, ens160, etc.

Potential References

hashicorp/packer#10168