Jira (FACT-1413) External facts do not override custom Ruby facts that have confines or a non-default weight

[James Sweeny (JIRA)]

Title: Message Title

James Sweeny created an issue   Facter / FACT-1413 External facts do not override custom Ruby facts that have confines or a non-default weight Issue Type: Bug Assignee: Unassigned Created: 2016/05/10 1:50 PM Priority: Normal Reporter: James Sweeny In Facter 2.x, external facts (txt, yaml, json, etc.) would override the value set by custom Ruby facts and core facts. In Facter 3, this is the case only when the Ruby fact being overridden has no confines and a default weight. When a custom Ruby fact in Facter 3 sets one or more confines, it will override all external facts. Desired behavior is that external facts override Ruby facts. When a custom fact without confines should be overwritten by an external fact: [root@server ~]# facter -p testfact RIGHT [root@server~]# cat /opt/puppetlabs/puppet/cache/lib/facter/test.rb Facter.add('testfact') do setcode do 'WRONG' end end [root@server~]# cat /etc/puppetlabs/facter/facts.d/testfact.yaml --- testfact: 'RIGHT' When a confine is added: [root@server~]# facter -p testfact WRONG [root@server~]# cat /opt/puppetlabs/puppet/cache/lib/facter/test.rb Facter.add('testfact') do confine :kernel => 'linux' setcode do 'WRONG' end end A workaround is available by setting `has_weight 0` in the Ruby fact, but this could result in a non-deterministic resolution order if there are multiple Ruby facts that use confine. Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.