Jira (FACT-1870) Stdout in facts invalidates formatted output (yaml/json)

[Eric Sorenson (JIRA)]

Title: Message Title

Eric Sorenson commented on FACT-1870   Re: Stdout in facts invalidates formatted output (yaml/json) FWIW I confirmed that using the Facter.error helper method in the rescue block provides clean STDOUT/STDERR separation - So with the fact below, facter -p -j | jq . works even with the error-generating output. The fact that these helper methods and best practice is folklore is a problem, which recent doc updates will help address, but it needs more developer-centric attention. Facter.add('test') do confine :kernel => 'Linux' begin test = 'nomatch' test = Facter.value(:doesntexist).strip() setcode { test } rescue Exception => ex Facter.error "#{File.basename(__FILE__)} - ruby fact threw an exception: #{ex}" end end eric@cloudline> facter -j --custom-dir ~/.puppetlabs/etc/facter/lib >/dev/null 2018-08-17 13:29:09.912197 ERROR puppetlabs.facter - error while resolving custom facts in /home/eric/.puppetlabs/etc/facter/lib/myfact.rb: undefined method `error' for Facter:Module eric@cloudline> facter -j --custom-dir ~/.puppetlabs/etc/facter/lib 2>/dev/null | jq . | head -2 { "aio_agent_version": "5.5.0", Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.