So, we ran across this one today and I dug up the thread where Felix Frank, John Bolinger, and I all agreed (https://goo.gl/LQ20bj) that there were solid use cases for keeping the Webrick version of Puppet around.
We were all fine with losing Rack support but, as of right now, I do not know how to debug the internals of the server-side Ruby code within the Clojure stack. As far as I can tell, I can't do the following in Puppet Server: 1) Stuff Pry into the middle of the stack and interact with it so that you can inspect the internal state of the Puppet Master process while testing custom types, functions, and providers. 2) Easily debug the *server* portions of the Ruby code 3) Spin up a lightweight Puppet server instance for trying/debugging some code on a laptop of limited resources Looking over PUP-4435, I don't see any indication as to exactly *why* we can't keep Webrick support or how to do the three items above. Digging into the referred ticket of PUP-4394, it seems like it would be relatively easy to either gracefully bail if the puppet user/group don't exist or, alternatively, to create them as an option. Yes, throw all sorts of "don't use this in production" warnings, but I need to know how to do the three things above prior to losing Webrick support because the code in 'puppet apply' doesn't work the same way as the puppet server compiler in all cases. Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 -- This account not approved for unencrypted proprietary information -- -- 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/CANs%2BFoXmWeE0eU7XeGe_-y4YWuL35Kf8%3DjZLf0abK-_p%3DTK51w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
