Jira (FACT-3003) Don't split keys for already structured json/yaml external facts

[Nick Walker (Jira)]

Title: Message Title

Nick Walker commented on FACT-3003   Re: Don't split keys for already structured json/yaml external facts If the users intent is to make a structured fact with a dot in the name of the fact there are 2 ways 1. ruby custom fact Facter.add( "a.b" ) do setcode do { c = true } end end 2. an external fact ( either a script of a json/yaml file ) { "a.b": { "c": true } } Given these two examples it does not make sense to treat a json/yaml file on disk differently than the Facter.add example. If the users intent is to have a structured fact with dots in the name we have no way of knowing that from either of these examples. Both examples appear the same and both will result in the fact a = { b => { c => true } } } in Facter 4 which is new behavior compared to Facter 3 which would have made a.b = { c => true } . This ticket is closed as won't fix because we're assuming we want to keep the behavior of Facter 4 treating dots specially. If we want to revert that behavior it's a different request altogether. Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.393500.1617226466000.179756.1617294660027%40Atlassian.JIRA.