On Tue, Nov 9, 2010 at 8:40 PM, Edward Bailey
wrote:
> Sure I can update the wiki - I hope I can save some else time the next time
> this come up.
>
> I like your suggestion, but I cant quite visualize how I could write a fact
> that will parse any files in /etc/fact.s and create separate facts fr
Sure I can update the wiki - I hope I can save some else time the next time
this come up.
I like your suggestion, but I cant quite visualize how I could write a fact
that will parse any files in /etc/fact.s and create separate facts from the
output. Would I use some sort of loop or will facter par
On Tue, Nov 9, 2010 at 6:01 PM, Edward Bailey
wrote:
> The purpose behind setting up the fact this way is that I thought it would
> be an easy way to populate servers with extra metadata without having to
> drop a file and then a fact with some shell code on every server.
>
> For example, we have
The purpose behind setting up the fact this way is that I thought it would
be an easy way to populate servers with extra metadata without having to
drop a file and then a fact with some shell code on every server.
For example, we have a number of servers that simply cannot be identified as
being p
On Tue, Nov 9, 2010 at 3:45 PM, wrote:
> ok - that makes sense, but why does facter have a feature
> http://docs.puppetlabs.com/guides/faq.html#can-i-access-environmental-variables-with-facter
> where you can expose environmental variables as facts if puppet will not
> recognize the facts? Is the
ok - that makes sense, but why does facter have a feature
http://docs.puppetlabs.com/guides/faq.html#can-i-access-environmental-variables-with-facter
where you can expose environmental variables as facts if puppet will not
recognize the facts? Is the issue because of the old version of facter
