Jira (HI-341) Hiera should support native HOCON to match Puppet Server

[J.D. Welch (JIRA)]

Title: Message Title

J.D. Welch commented on HI-341   Re: Hiera should support native HOCON to match Puppet Server So, we intend to use a .hocon extension for those data files. That sounds reasonable. Except. I can't find anything other than a ticket at the typesafe/config project that mentions the extension as a thing that exists in the world. So I'll step back to be an ass and suggest: Why do we need to do this anyway? If Hiera is intended to read machine-optimized data files, what's wrong with JSON? I get the consistency argument for configuration file format. If we're talking about a totally separate problem, is HOCON actually suited to solving it? Separately, we may want to have a discussion in the future about whether our existing HOCON config files in Puppet/PE should also be renamed from .conf to .hocon, but since that would be a costly and disruptive change, we do not intend to pursue it for now. Please don't do that. The conf.d/foo.conf pattern is clear and reasonable. Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.