Puppet compatibility – or lack of
Whilst playing with the [http://reductivelabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0/ puppet-dashboard] I noticed some warning notices in my puppetmaster logs. Now all file resource types must prefix “module” (although templates don’t need to!).
It’s only a small change, but please can these things be done a bit more sanely? By this I mean a documented approach to when these changes will be phased out – and when there is an overlap for compatibility. At the moment it’s all rather piecemeal which makes supporting puppet across multiple versions much more difficult that it should be.
I know the release notes do state these things – which _is_ very helpful. It would just make the product seem much better thought out and designed if the language evolved along a known roadmap rather than what often seems to be a “oh, we are changing this as it makes some internals a bit cleaner”. At least it’s better than the alternative (not cleaning it up). Puppet is still at the early adopter stage after all.
Posted: January 18th, 2010 under Linux, Linux Rants.
Comments: 1
Comments
Comment from shihan
Time: Friday 10 June, 2011, 10:16
I hate these guys for not staying compatible between different versions! Every time you update a server (debian, ubuntu) you have to upgrade or downgrade puppet – most of the time manually or by using backports. Annoying and time consuming. I thought their tool should save time!
Write a comment