Issue #10264 has been updated by Ken Barber. Status changed from Unreviewed to Needs More Information
Garett, Are you seeing this bug using the PE instructions for facts.d? This is a completely different implementation then what will be provided in 1.7.x I just want to know what to do with this bug. If you see issues with users using facts.d with the official PE documentation then it should be raised there. If its just a case that users are reading the online docs and trying to implement that mistakenly in PE - we can request that doc be pulled for now until 1.7.x be released. ken. ---------------------------------------- Bug #10264: facts in facts.d do not show up when running facter from the command line https://projects.puppetlabs.com/issues/10264 Author: Garrett Honeycutt Status: Needs More Information Priority: Normal Assignee: Category: Target version: Keywords: Branch: Affected Facter version: 1.6.0 Following http://docs.puppetlabs.com/guides/custom_facts.html, I placed a custom fact in /etc/puppetlabs/facter/facts.d/myfacts.txt with the contents <pre> myfoofact=foo </pre> When accessing this fact via a manifest, such as the following in the site manifest, it works. <pre> node 'some.node' { notice("myfoofact is ${myfoofact}") } </pre> However when running `facter myfoofact` the fact is not found. This behavior is quite confusing to people. I have seen multiple people give up saying that the custom facts are broken before even trying to use them via a manifest. -- 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.
