Bumping this thread, prompted by Josh Hoblitt's comment about the PRFC process.
There was some good commentary on the doc, thanks very much for that. it seems like the main outstanding question is the name of the Puppet module which manages the resources; Reid commented in the doc that it seems "presumptuously generic" to call the defined type `http_authorization::rule`; I kind of disagree but don't have super strong feelings about it and can definitely see the point. Any opinions? I'd like to get that resolved pretty quickly. Once we resolve this question I'll push the RFC through to "Funded". --eric On Monday, September 14, 2015 at 11:55:15 AM UTC-7, Eric Sorenson wrote: > > Hi, I posted a design doc I wrote around the current state of the > Clojure-based auth.conf replacement that Brice wrote as a Puppet RFC. > Here's the public google doc link: > > > https://docs.google.com/document/d/1XIsGAg0Dm_aF5YWzvzZwkYaGQ15XoLVONCgYiBv9RpI/edit > > Please feel free to read and comment. There have been some good > discussions here on puppet-dev earlier so much of it is underway, but it'd > be great to have feedback as some of the details have evolved around rule > sort order, match parameters, etc. > > Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 > puppet platform // coffee // techno // bicycles > > -- 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/3627191a-7d19-485d-92f8-0107de674462%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
