Boolean attribute that allows bypassing of the hosts IP to the hostsfile.

[xamebax]

Hi, could you explain why this would be useful to have?

[brenttheisen]

Sure. Without something like this the chef recipe will always write a /etc/hosts entry for the node it runs on. You can configure the IP it puts in there so it isn't always the loopback IP but I don't want to have to specify that for every node. Instead, I already have a internal DNS server that will resolve the node's hostname for me so I just want this chef recipe to set the hostname without writing an /etc/hosts entry for it.

[mpasternacki]

The use case is good; desired behaviour depends on /etc/resolv.conf and its search setting or the internal DNS resolving unqualified names, but I'd say this is outside this cookbook's scope. The changes are not ready to merge, though. Please:

• [ ] fix the failing foodcritic remark (see Travis)
• [ ] add chefspec test case for the new feature (there doesn't seem to be need for a whole test-kitchen integration test case)
• [ ] document the new attribute in README

When that is done, I'll merge the change and release new version.

[brenttheisen]

Deleted old branch and pushed new one with changes as requested. I can use my fork for the foreseeable future so no need to push a release on my account.

[brenttheisen]

Rebased to get rid of merge conflicts.

[xamebax]

Hi, very sorry for not responding for so long. The Travis build is failing here (old gems I guess), but I fixed it on develop. If I'm not mistaken, when you merge develop in, everything should be working fine and dandy.

[mburns]

I'm generally positive towards this change, but there has bit some bitrot due to inaction. I'm closing this in favor of #44