Issue #2560 has been updated by Markus Roberts. Status changed from Accepted to Duplicate
The problem was that it was always/only looking at @site.pp@ (see #2559). Thanks for the bug report, having multiple perspectives on these sorts of errors helps triangulate & find the root cause. ---------------------------------------- Bug #2560: The --parseonly option fails to flag parse errors http://projects.reductivelabs.com/issues/2560 Author: Todd Zullinger Status: Duplicate Priority: High Assigned to: Markus Roberts Category: parser Target version: Complexity: Unknown Affected version: 0.25.0rc1 Keywords: Using the stand-alone puppet script from 0.25.0rc1 to check for syntax errors fails to flag obvious parse errors: <pre> $ cat bad.pp file { '/etc/foo': owner => 'root' group => 'root' mode => 0644, } $ puppet --color=false --confdir=. --parseonly --ignoreimport bad.pp $ echo $? 0 </pre> The missing commas are not noticed. Using 0.24.8 produces the desired results: <pre> $ puppet --color=false --parseonly --ignoreimport bad.pp err: Could not parse for environment production: Syntax error at 'group'; expected '}' at /home/tmz/bad.pp:3 $ echo $? 1 </pre> (See bug #2559 for the reason that --confdir was needed.) -- 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://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
