Jira (FACT-622) changes to ordering in custom facts breaks things

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: changes to ordering in custom facts breaks things When Facter runs, it tries to do so in two passes - the first pass loads fact files and should not actually evaluate facts, and the second pass actually evaluate facts. However, if you do something like this: # somefact.rb Facter.value("something") This forces the evaluation of something at load time, which can cause bad behaviors with loading. To avoid this, write your facts like so: Facter.add("some_fact_that_needs_something") do setcode do Facter.value("something") # ... end end This will prevent the something fact from being evaluated until after all facts have been loaded. Add Comment   Facter / FACT-622 changes to ordering in custom facts breaks things *edit* Looks like this also exists in 2.0.1 - so this may just mean that our custom facts aren't backwards compatible with the new loading logic. Is there a way to order facts if they are sourced from two different files, so that one depends correctly on the other, without filename precedence? *edit* We have a set of custom fact called node_type.rb whi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.