Issue #12438 has been updated by Stephen Gran.
Hi, Yes, that seems like a sensible approach. I had contemplated leaving 'name' as the primary key, but introducing something like 'hostname' which defaults to 'name' but could have a different value (and 'hostname' is what ends up in /etc/hosts), as this would allow people to model more complicated setups. Your approach also allows for this, I think, although yours has more safety over only allowing one entry per IP into /etc/hosts. Whether that is a good thing or not is possibly a moot point, but I think it's a reasonable approach to take. Cheers, ---------------------------------------- Bug #12438: host type does not understand multiple IP addresses https://projects.puppetlabs.com/issues/12438 Author: Stephen Gran Status: Duplicate Priority: Normal Assignee: Category: host Target version: Affected Puppet version: Keywords: host type Branch: Two things that currently can not be represented with the host type are: <pre> sgran@harris:~$ getent hosts google.com 173.194.67.99 google.com 173.194.67.104 google.com 173.194.67.103 google.com 173.194.67.106 google.com 173.194.67.105 google.com 173.194.67.147 google.com </pre> and ipv4/ipv multi-homed hosts. I understand that there is a lot of existing config that assumes that 'ip' is a single parameter, so the provider will have to do something like to_a.flatten before using the provided line as an array. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
