Jira (FACT-3192) Custom fact fails to appear when using some options like --json

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper commented on FACT-3192   Re: Custom fact fails to appear when using some options like --json root@pe-server-238c28-1 development (development)$ facter --json | grep -E "(oslogin|[^/]bigbird)" "oslogin": { This output (above) is expected because bigbird is a custom fact in a puppet module (so --puppet is required to load those facts) root@pe-server-238c28-1 development (development)$ facter -p --no-external-facts | grep -E "(oslogin|[^/]bigbird)" [2023-03-17 13:28:08.334765 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one This output (above) is not expected and is a bug. The "--no-external-facts" command line option is important because it prevents recursion when external facts call facter. See FACT-1373 and that was added in Facter 3 and the same issue again in Facter 4 (FACT-2772) Add Comment   This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.483146.1679060554000.2363.1679448660042%40Atlassian.JIRA.