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.
Learning curve for a newcomer is steep high, but even once you're
seasoned puppet engineer, amount of changes happening is overwhelming.
It just becomes a time sink, and wastes a lot of your time just to keep
your code base up to date.
And sincerely I don't see any obvious benefit of some of these additions
(epp, moving from lose to strict parameter/variable types, ...).
It's something to think about: is puppet becoming it's own goal and
purpose (losing sight of what it should be - a tool that solves actual
problems)?
--
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/6a7d7f3d-6475-0109-6f23-c5ff39840bf6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
