Parsing issues in 3.5

[Joe Topjian]

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 manifests besides defined types. Two examples are:

https://github.com/saz/puppet-rsyslog/issues/74

https://github.com/arioch/puppet-redis/blob/master/manifests/init.pp

For the Redis example, I had to add redis:: to each of the include statements and Class resources. I understand why those changes needed made, but I don't understand what caused them to appear in 3.5.x when everything works fine in 3.4.

I read that Puppet 3.6 fixes some issues with the future parser. Are the issues I'm seeing known and fixed?

Thanks,

Joe

[Henrik Lindberg]

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 it, please file a ticket in that case.

Regards

- henrik

> Thanks,
> Joe
>
> --
> 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...@googlegroups.com
> <mailto:puppet-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/94532ad1-75c3-48c3-92a9-0bcd583e1133%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/94532ad1-75c3-48c3-92a9-0bcd583e1133%40googlegroups..com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.


--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

[Joe Topjian]

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 current but not under --evaluator future,
we like to hear about it, please file a ticket in that case.

I apologize for the late reply!

Thank you for your reply and information. I'm away from the office this week, but will try this out as soon as I have a chance.

Thanks again,
Joe

[Joe Topjian]

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 it, please file a ticket in that case.

Again, sorry for the late reply, but I wanted to confirm that setting evaluator to current did resolve the issue. I'll file a ticket now.

Thanks,

Joe