> What's the benefit to making it part of Puppet except for having a
> single tool to deal with? Is the investment of time worth the return?
>
>
I think one simple use case is someone would want to track /etc to figure
out if they need to put any additional files under Puppet management, but
don't neccessarily need to want to research/learn/setup/maintain the other
tool(s).    Setup of that integration is larger effort unless you say
'Puppet requires foo', (which also makes Puppet harder), so in that case it
seems to make sense to include something lightweight in Puppet ... but
assume it's probably not indexing anything by default.

--Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" 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-dev?hl=en.

Reply via email to