Jira (FACT-79) Facter built-in legacy facts are inconsistent in type - convert to string and add simple schema

[Joshua Hoblitt (JIRA)]

Title: Message Title

Joshua Hoblitt commented on an issue   Re: Facter built-in legacy facts are inconsistent in type - convert to string and add simple schema I'll admit that I was a bit skeptical of the json schema approach when I first heard about it but after looking at PR 581 I'm pretty enthusiastic about this approach since it's done as a regression test rather than at runtime. My vote would be for a strong policy of maintaining the return types of stable/1.7 facts as they are now essentially forever (or at least through ~> 2) and only fixing the cases where a different type could be returned � essentially making the return type invariant for all existing types. Add Comment   Facter / FACT-79 Facter built-in legacy facts are inconsistent in type - convert to string and add simple schema I just saw a ticket go past from the PuppetDB team about stringification to work around a test failure due to data type changes, and I think they hit the same issue we did: Facter is actually pretty bad at imposing the ABI that Puppet strongly suggests it has. We hit this in the Microkernel for Razor in about the same way: we get facts from Facter... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.