You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so puppet-lint says there is a syntax error, but the puppet parser validate command is silent (so says it's ok).
Once I convert the file with dos2unix the problem disappears.
The request is to please either:
handle files that are in DOS mode,
OR
give a warning that the file is in DOS mode instead of giving a 'syntax error' while not specifying what is wrong in the syntax.
The text was updated successfully, but these errors were encountered:
This is a feature request to fix a small annoyance I ran into:
When I have a manifest in DOS line endings mode and then run puppet-lint, I sometimes (depending on the manifest) get this:
[max@zd007 hooks]$ puppet-lint --no-80chars-check --no-hard_tabs-check --no-2sp_soft_tabs-check --no-trailing_whitespace-check --log-format "%{KIND} %{check} says %{message} for %{filename} on line %{linenumber}" /home/m.vernimmen/svn/puppet/modules/staging/fredhopper/manifests/init.pp --with-context
ERROR unknown says Syntax error (try running
puppet parser validate <file>
) for init.pp on line 329if ($hostname !~ /^pd0/) {
^
[max@zd007 hooks]$ puppet parser validate /home/m.vernimmen/svn/puppet/modules/staging/fredhopper/manifests/init.pp
[max@zd007 hooks]$
so puppet-lint says there is a syntax error, but the puppet parser validate command is silent (so says it's ok).
Once I convert the file with dos2unix the problem disappears.
The request is to please either:
handle files that are in DOS mode,
OR
give a warning that the file is in DOS mode instead of giving a 'syntax error' while not specifying what is wrong in the syntax.
The text was updated successfully, but these errors were encountered: