(#9080) Add facts from /etc/puppetlabs/facts.d #14
Conversation
This fact is a direct copy of R.I.'s work at https://github.com/ripienaar/facter-facts This is necessary plumbing to allow the installer to write a simple text file based on the role the node is receiving. For example: $ cat /etc/puppetlabs/facts.d/puppet_enterprise_mcollective.txt fact_stomp_port=61613 fact_stomp_server=puppetmaster fact_is_puppetagent=true fact_is_puppetmaster=true The mcollectivepe module relies on these facts being set and we need a persistent place to write them during the interview process and later read them when puppet agent runs to configure MCollective on the agent systems. Since stdlib is a public module, both /etc/facts.d and /etc/puppetlabs/facts.d are scanned for static facts.
|
You should at least be consistent with what's happening in Facter here - it looks like we're using /etc/facter/facts.d, which is what Mike decided on. |
|
On Wed, Aug 17, 2011 at 8:29 PM, lak <
Do you know if Facter's facts.d feature is API compatible with RIP's If they are, I'm happy to make it use the same path, but if they're -Jeff |
|
On Thu, Aug 18, 2011 at 9:26 AM, jeffmccune <
You're right - I don't think they're compatible, and it makes sense to keep |
This fact is a direct copy of R.I.'s work at
https://github.com/ripienaar/facter-facts
This is necessary plumbing to allow the installer to write a simple text
file based on the role the node is receiving. For example:
The mcollectivepe module relies on these facts being set and we need a
persistent place to write them during the interview process and later
read them when puppet agent runs to configure MCollective on the agent
systems.
Since stdlib is a public module, both /etc/facts.d and
/etc/puppetlabs/facts.d are scanned for static facts.