Comments on: Iteration in Puppet using the future parser https://blog.bluemalkin.net/iteration-in-puppet-using-the-future-parser/ A blog about DevOps technologies, tips and tricks. Wed, 02 Oct 2024 03:08:46 +0000 hourly 1 https://wordpress.org/?v=4.9.8 By: Tom Murphy https://blog.bluemalkin.net/iteration-in-puppet-using-the-future-parser/#comment-16684 Mon, 24 Nov 2014 08:52:50 +0000 http://blog.bluemalkin.net/?p=167#comment-16684 Hi Larry,

Enabling the future parser can break quite a few things, as it requires all the Puppet code to adhere to the language restrictions (see https://docs.puppetlabs.com/puppet/latest/reference/experiments_future.html#new-language-restrictions ).

The best way to check that the new language restrictions are compliant, is to view the syslog on the Puppetmaster. Then your catalogues should compile.

]]> By: Larry Liu https://blog.bluemalkin.net/iteration-in-puppet-using-the-future-parser/#comment-16232 Fri, 21 Nov 2014 18:13:55 +0000 http://blog.bluemalkin.net/?p=167#comment-16232 Hi
According to puppetlab’s doc, parser=future is supposed to work with puppet version 3.3 or higher. Your doc looks great too. I’m on 3.7.1 which falls under https://docs.puppetlabs.com/puppet/latest/reference/experiments_future.html, but it has not worked for me at all. Interestingly it works fine if I run just CLI puppet apply –parser=future xyz.pp. Once I enable it on my puppet masters, clients just keep getting ‘Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Do not add methods to model classes directly, add them to the ClassModule instead on node xxxxxx’. The ruby version on both masters and clients is ruby-1.8.7.352-13.el6.x86_64.

Any idea know why?

]]>