Issue #21874 has been updated by eric sorenson. Target version changed from 3.4.0 to 3.5.0
This pull request dropped off the board for 3.4.0, will address in the next version. ---------------------------------------- Bug #21874: Enabling --parser future causes classes to be not found and other errors https://projects.puppetlabs.com/issues/21874#change-100233 * Author: Lee Lowder * Status: In Topic Branch Pending Review * Priority: Normal * Assignee: Henrik Lindberg * Category: parser * Target version: 3.5.0 * Affected Puppet version: 3.2.2 * Keywords: future_parser customer * Branch: https://github.com/puppetlabs/puppet/pull/2020 ---------------------------------------- (from a customer) After setting parser = future in puppet.conf, code that was working now causes errors. Sample error: undefined method `value' for Puppet::Pops::Model::AccessExpression:Puppet::Pops::Model::AccessExpression at /etc/puppetlabs/puppet/modules/.../manifests/logic.pp:24 (code sample is in the support ticket, will be linked to in a comment) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
