IMHO, the changes made to the language in 4.x allows for better and more complete modeling of systems. Yes you have more 'things' to learn, the types/lookup systems for example but they are relatively simple to understand. Look at your ntp example, I image it was the specification of Types that looks so different and it is but your get assurances that your classes parameters receive data it can use. You don't need an army of validators. This is a good thing.
The rapid development of a system and its supporting structures is not a sign of rot it's quite the opposite. Keep in mind as well that puppet is NOT a scripting language that lets you setup ntp on your nodes. It's a modeling language that lets you express the important features of your system(s). At times that can look like over-engineering and it is if the perspective you have is 'I just need my ntp config pushed to my box' but I'd posit that your missing the forest for the trees. The ntp model should model the ntp system with sufficient suppleness that it is generally applicable AND able to handle more advanced use cases. If that is not an important feature if the systems you are modeling, don't use it. File[] is always there 😉 On Sun, Jan 8, 2017, 9:58 AM Fabrice Bacchella <fabrice.bacche...@orange.fr> wrote: > > > Le 8 janv. 2017 à 14:54, Jakov Sosic <jso...@gmail.com> a écrit : > > > > On 01/08/2017 11:04 AM, Fabrice Bacchella wrote: > > > >> And that's for something that for a given environment > > > never change, have no options. So dropping a standard > > > file that is hand made once in a lifetime is enough for > > > the vast majority of people. > > > > Exactly my point... > > > > I never really understood all the blog posts about people migrating to > other tools, and didn't quite understand bunch of the remarks and reasons > given in those posts...let alone agree with them. > > > > But, becoming such a time sink even for a veteran is kinda depressing. I > can even see my self writing such a blog post in the future :D > > > > Sure, organizations having 10+ devops engineers can afford to allocate > one of them 0.5/1.0 FTE on puppet alone, but smaller shops with 2-5 devops > engineers just can't afford it. > > > > They can, by dropping so called 'best practice' from puppet, but instead > stick to KISS. Like don't build files that can just dropped, don't > automatise what is done once in life time, puppet mode are data, not code. > So I fell happy to put specific code for my own plate form in them. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/F4C5D70E-9FF4-4257-9B23-1E21250B0510%40orange.fr > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACx1-q3vthX4_E_vE5MrRdicHt-PtB_M7a16%2BOX2A-3xc2hOqg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
