You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have the IP resolving logic always use the ip_resolver Proc, and implement the default behavior (of using private_network or ssh_info) as a Proc itself. This way we can eventually have built-in resolvers for different use-cases.
For example, as in #86, reading an interface's ip address in a DHCP scenario could look something like this:
I'd like to have the IP resolving logic always use the
ip_resolver
Proc, and implement the default behavior (of using private_network or ssh_info) as a Proc itself. This way we can eventually have built-in resolvers for different use-cases.For example, as in #86, reading an interface's ip address in a DHCP scenario could look something like this:
This would find the dhcp resolver and instantiate it with the option
interface: "eth1"
.Before implementing this, I'd like do some refactoring as per #99. I'm just putting this here so it's not forgotten.
The text was updated successfully, but these errors were encountered: