i've seen this in both native and ruby facter. if you define an external non-executable fact containing a space in an ini txt file, and there are spaces around the '=' the fact key appears to have a trailing space in it. In facter2, IIRC you can get the fact using 'foo ', but this doesn't appear to work in native facter. In either case you can find the fact in the entire output with grep. ./external/foo.txt
i've seen this in both native and ruby facter. if you define an external non-executable fact containing a space in an ini txt file, and there are spaces around the '=' the fact key appears to have a trailing space in it. In facter2, IIRC you can get the fact using 'foo ', but this doesn't appear to work in native facter. In either case you can find the fact in the entire output with grep. ./external/foo.txt
i've seen this in both native and ruby facter. if you define an external non-executable fact containing a space in an ini txt file, and there are spaces around the '=' the fact key appears to have a trailing space in it. In facter2, IIRC you can get the fact using 'foo ', but this doesn't appear to work in native facter. In either case you can find the fact in the entire output with grep. ./external/foo.txt {code} foo = bar bar=foo {code}