Hi Henrik,
In 3.5 the new evaluator was added and it is on by default when using
> --parser future. If you want to turn it off you can use --evaluator
> current in addition to --parser future)
>
> If it works under --evaluator current but not under --evaluator future,
> we like to hear about i
Hi Henrik,
On Saturday, May 10, 2014 2:56:19 PM UTC-4, Henrik Lindberg wrote:
In 3.5 the new evaluator was added and it is on by default when using
> --parser future. If you want to turn it off you can use --evaluator
> current in addition to --parser future)
>
> If it works under --evaluator
On 2014-09-05 19:22, Joe Topjian wrote:
Hello,
I keep running into several parsing issues in 3.5 that don't exist in
Puppet 3.4.
I saw the thread about issues with the future parser and defined types:
https://groups.google.com/forum/#!topic/puppet-users/HOVnQ1EXwjY
I'm using the future parser
Hello,
I keep running into several parsing issues in 3.5 that don't exist in
Puppet 3.4.
I saw the thread about issues with the future parser and defined types:
https://groups.google.com/forum/#!topic/puppet-users/HOVnQ1EXwjY
I'm using the future parser, but I'm seeing issues in other manifest
I'm running into a very odd occurrence. I started with a new puppet
server and was able to add a few classes, however as I try and add new
ones I get odd parsing error messages, the most common being Could not
match '}' at whatever file.
Here is the exact error I get
err: Could not retrieve ca
