Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper commented on FACT-1858   Re: Provide an option to disable legacy facts so they are not sent to the master from the agent We attempted to disable legacy facts many years ago by blocking them in facter. However, that breaks types and providers that confine/defaultfor based on legacy facts, like the builtin "init" service provider: $ puppet apply -e '' Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass In order to disable legacy facts without breaking agents and provide a graceful migration path, we need to handle this in puppet, not facter. I've filed PUP-11662, which will make it possible to disable legacy facts in puppet 7.x. In puppet 8, we will fix puppet's builtin types/providers to reference structured facts and disable legacy facts by default (PUP-11430). Therefore, I'm going to close this as a duplicate, superseded by the puppet tickets. 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.253867.1527713421000.53289.1666886280165%40Atlassian.JIRA.