Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Syntax error (try running puppet parser validate <file>) on line 15 #258

Closed
lmayorga1980 opened this issue Mar 18, 2014 · 1 comment · Fixed by #293
Closed

ERROR: Syntax error (try running puppet parser validate <file>) on line 15 #258

lmayorga1980 opened this issue Mar 18, 2014 · 1 comment · Fixed by #293
Milestone

Comments

@lmayorga1980
Copy link

It seems that puppet-lint doesn't like the parser future syntax.

class netfx($version) {

  each($version) |$ver| {

    file { "dotNetFx${ver}":
      ensure => present,
      path   => "C:\\Temp\\dotNetFx${ver}.exe",
      source => "puppet:///puppetfs/netfx/dotNetFx${ver}.exe",
      mode   => '0755'
    }

    package { "dotNetFx${ver}":
      ensure           => installed,
      name             => "Microsoft .NET Framework ${ver}",
      source           => "C:\\Temp\\dotNetFx${ver}.exe",
      install_options  => [ '/q', '/norestart' ],
      require          => File["dotNetFx${ver}"]
    }
  }
@rodjek
Copy link
Owner

rodjek commented Apr 2, 2014

Indeed it doesn't. When the future parser stabilises and stops being experimental, I'll add support. Support for the pipe character has been added to the parser in master though so it'll no longer throw a syntax error when it encounters it.

rodjek added a commit that referenced this issue Aug 17, 2014
Adds support for future parser loop local scope blocks that define variables
to the variable_scope check.

Closes #264
Closes #258
Closes #249

/cc #271
@rodjek rodjek added this to the 1.0.0 milestone Aug 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants