Thanks for the feedback, everyone - I've incorporated as much as I could into the doc and have a PR against the Puppet-RFC repo with the draft content. Please continue to post questions/comments on this thread.
John -- I think the comments on your HOCON question were constructive, but I fear they were not convincing. I looked back through the archives and realized that all of the discussions (which were, as Ryan W noted in the comment, pretty heated) about the introduction of that format happened on internal lists. This was wrong, and I now have a TODO item to more clearly describe the rationale behind and support statements for the use of Hocon around Puppet's ecosystem. --eric0 On Thursday, July 7, 2016 at 5:42:50 PM UTC-7, Eric Sorenson wrote: > > Hey all, I completed this write-up, any comments/feedback appreciated. > > > https://docs.google.com/document/d/1xlj0NYESLHNv5ZO_NJ-1fCssAWzaHsTZIhyaK3uzHQY/edit# > > I also put a PR against the puppet-specifications repo showing the > filesystem locations in case it's easier for you to visualize this way: > > https://github.com/puppetlabs/puppet-specifications/pull/79 > > Fire away... > --eric0 > > On Tuesday, March 1, 2016 at 10:52:12 AM UTC-8, Eric Sorenson wrote: >> >> I've been thinking about a config file for Facter, which has historically >> not been run-time configurable. >> >> The two problems in front of me that seem applicable are: >> >> * Sometimes, certain facts are just plain bad to collect and users would >> like to prevent them from even being resolved (see FACT-718, FACT-449, ). >> * Some facts are not inherently bad but _are_ expensive and/or change >> infrequently, so preventing them from being resolved every time would be >> beneficial (FACT-348) >> >> Are there other problems you're running into in this area that you'd like >> to see addressed with a "facter.conf"? I'd like to gather all the >> requirements and start up a little Puppet RFC based on them. >> >> --eric0 >> >> -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/1497462f-3c1f-44a8-9cfe-41e68d73afb6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.