Project

General

Profile

Actions
Copy link

Bug #2878

closed

Import Classes fails when using parser = future

Added by Tomas Edwardsson over 12 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Puppet
Target version:
1.4.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

I have manifests which use the 3.2 experimental features described in http://docs.puppetlabs.com/puppet/3/reference/lang_experimental_3_2.html using parser=future in the [master] section.

Version: foreman-proxy-1.2.0-1.el6.noarch

I'm getting the following error in the smart proxy access.log

Error while parsing /etc/puppet/modules/ok_development/servicedesk/manifests/mail/config.pp: Syntax error at '.'; expected '}' at line 11
Error while parsing /etc/puppet/modules/ok_development/ssl_cert/manifests/init.pp: Syntax error at '.'; expected '}' at line 2

Line 11 contains:

        $map_emails.each |$index, $value| {

One of the manifests that fail looks like this:

class servicedesk::mail::config( $apikey, $apiurl, $ignore_senders, $save_all_mails, $map_emails) {
        file { "/etc/servicedesk/mail.ini":
                owner => root,
                group => mail,
                mode => 640,
                content => template("servicedesk/mail.ini.erb"),
        }

        include mtr

        $map_emails.each |$index, $value| {
                $alias = regsubst($index, '@', '-')
                mtr::sendmail::config::map_entry { $index:
                        recipient => "servicedesk-mail-${alias}",
                        entry_type => 'virtusertable' }
                mailalias { "servicedesk-mail-${alias}":
                        recipient => "| /etc/smrsh/servicedesk-mail ${value}" }
        }
}

Actions
Copy link

Also available in: Atom PDF