[FACT-1284] Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result - Puppet Jira Server

XML

Word

Printable

Release Notes:
Bug Fix
Release Notes Summary:
Facter::Util::Resolution.exec will now set the Ruby $? exit status variable

The following worked with Facter 2, but produces an error in Facter 3.

Facter.add("foo") do

  setcode do

    Facter::Util::Resolution.exec('echo hello')

    $?.exitstatus == 0

end

end

Output is

2015-12-12 12:04:56.346097 ERROR puppetlabs.facter - error while resolving custom fact "foo": undefined method `exitstatus' for nil:NilClass

Facter::Util::Resolution.exec no longer sets $? to a Ruby Process::Status object.

relates to

FACT-2934 Facter::Core::Execution does not set status variables in Facter 4

PA-304 Update to Leatherman 0.6.1

FACT-1769 Ruby API for command execution with status code in result