When custom-dir is not an absolute path, Facter 4 logs a debug message and ignores the directory (behavior inherited from Facter 2) while Facter 3 accepts relative paths as custom-dir.
I suppose Facter 4 behavior should match Facter 3 behavior.
When custom-dir is not an absolute path, Facter 4 logs a debug message and ignores the directory (behavior inherited from Facter 2) while Facter 3 accepts relative paths as custom-dir.
I suppose Facter 4 behavior should match Facter 3 behavior.
{code:java} $ facter --custom-dir non-existing --debug 2>&1 | grep non-existing [2021-10-06 13:46:20.375087 ] INFO Facter - executed with command line: --custom-dir non-existing --debug [2021-10-06 13:46:20.376933 ] DEBUG LegacyFacter::Util::Loader - Excluding non-existing from search path. Fact file paths must be an absolute directory