On Fri, Jan 29, 2016 at 12:08 PM, Alex Harvey <[email protected]> wrote:
> The main issue I still have, and I just checked again, is that too many > Forge modules say in their documentation that they're only supporting > Puppet 3. E.g. Logstash, Nginx. Now, maybe in actual fact they work fine > in Puppet 4; and that was mostly my experience when I played with it. But, > you know, if someone's crazy Forge module doesn't work, users point the > finger at Puppet for that. While you can't force all the forge modules to be updated, I highly suggest setting up rspec-puppet on your controlrepo. You'll find the modules that don't support future parser with 3, or 4 in general, and file tickets with the module authors. I had to do that for a number of modules I use (ajjahn/dhcp and stahnma/epel ring a bell) and I found the authors are generally receptive. If they're not, then it might be a good indicator that you shouldn't be relying on that module; find another or fork it if the license allows you to. Heck, maybe some module authors are watching this thread and are seeing the demand for supporting Puppet 4 :) Rob Nelson [email protected] -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAC76iT9O6pofNB2%3DrWGu34%3DZaGkSVrcEhgO7EBGWUYd6pwUZ_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
