search for: parseon

Hi all, I''m considering moving --parseonly to just puppet, rather than it and puppetmasterd. Considering that it''s really only useful for parsing a specific file, puppet has the benefit of requiring that you specify that file directly. Since Puppet now supports multiple environments, --parseonly becomes both more diffic...

Hello, I was wondering if there is a way to parse individual manifest files as part of a pre-commit hook in subversion. I am looking for something like puppetmasterd --parseonly, but that will work on individual files. This way I can reject a commit if it does not pass. Any ideas? TIA

Hi everyone, I''m using a svn pre-commit hook to check manifests for syntax errors. I''ve recently upgraded puppet from 0.22.4 to 0.23.2 and the hook stopped working. I use the following command to parse .pp files: /usr/local/bin/puppet --confdir=/tmp --vardir=/tmp --parseonly --ignoreimport /tmp/$$.pp Now, I make a decision based on the exit code. If 0 then commit, else exit and show the error message. It looks like new puppet always returns 0 regardless if there were syntax errors or not. Is this normal? I''m doing this on FreeBSD 6.1 Cheers, Andrew...

...re committing them to version control and updating the production puppet server. I would like a script that could check the validity of the entire configuration. This would include both syntax errors and logic errors like including a class that isn''t defined. I have used "puppet --parseonly" but that seems to only check for syntax errors. Does anybody have a script like this? Is anyone else interested in this? My idea is that the script would do load the configuration like the server does. - Ian

This has been a much-requested feature, and is now a reality (in svn trunk): There is a new option, --ignoreimport, that will (surprisingly) ignore import statements. This is really only useful when using -- parseonly in a commit hook, and note that you''ll have to add the option to --parseonly, none of the puppet executables will add it for you. You should be able to parse-check a single file with something like this: puppet --parseonly --ignoreimport <file> Committed in [2302]. Als...

I''m running into a very odd occurrence. I started with a new puppet server and was able to add a few classes, however as I try and add new ones I get odd parsing error messages, the most common being Could not match ''}'' at whatever file. Here is the exact error I get err: Could not retrieve catalog: Could not parse for environment production: Could not match

...9;m trying to use pre-commit SVN hook for checking puppet syntax. For it I try to use some scripts from this thread: http://groups.google.com/group/puppet-users/browse_thread/thread/50ff2eb268f982da?pli=1 But when I try some of the scripts I see the common problem, expression like this: # puppet --parseonly --ignoreimport file.pp produces no output, but "file.pp" has a known broken syntax. What I need to change in this statement to see information about syntax errors at STDOUT? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To...

I would like to delegate access to puppet to other teams in our company. It has to be possible for them to: - create new recipes - doing some sort of check if their recipes / templates work. How should I do this without giving other teams the ability to create havoc? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this

...nt: No file(s) found for import of ''classes/*.pp'' at /repository/tmp_svn/7426.pp:4 so it fails on the import statement. I did a workaorund by placing | grep -v site.pp in the script. However it would be nice to test as well site.pp file. Maybe it''s possible to tell the --parseonly to ignore imports or so? thanks and greets pete

...to check syntax etc. I''ve been getting the following error: Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb": superclass mismatch for class ResourceOverride specifically small test pp files still work, though I''ve found when I use parseonly it doesn''t catch any syntax errors it always thinks they are ok. -- stickm@gmail.com -==< Stick >==- _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

...: { include debian } } include baseapps, sshd, admin, default } <=== line 7 node default inherits basenode {} I receive an error. err: Could not parse for environment production: Syntax error at ''}'' at /etc/puppet/manifests/templates.pp:7 when i run : puppet --parseonly --ignoreimport /etc/puppet/manifests/ templates.pp I verified the sytanx. But no luck. Still i have prbs. I require help with this. puppet version - 0.24.4-8 OS - ubuntu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google...

Hi, I want to validate my puppet manifests before I check them into source control. I just want to make sure that the manifest syntaxes are legal, not to do any more complex testing - the checkin may be on my laptop and not on the system that the manifests may be intended to run on. Ideally I''d be able to do this from ruby code - and I did try to instantiate some classes and override

hello,all. Is there a have some tools to check the puppet manifests before to use it ? like nagios -v nagios.cfg .the new version puppet client can''t get error syntax message,so ,when have some syntax error I can''t found it. -- Huang Mingyou

...ian package: * Better Rails query creation * Correct resource deletion from Rails * Empty configuration values are supported Parsing errors are correctly logged and correctly fails when there are syntax failures in unrecoverable circumstances, including --parseonly. Can someone using 0.23.2 put the code in the 0.23.x branch through its paces, just to make sure? I''ll plan on releasing tomorrow, or maybe early next week (I''ll be gone through the weekend, and I want to give people a chance to test). -- I had a linguistics professor...

...e Mercurial as my SCM system. So I was wondering if someone out there knows mercurial well enough to write a commit hook? I''ve tried myself, and came up with this: pretxncommit.parsecheck_puppet = hg log -v -r $HG_NODE | sed -n ''/ ^files:/{s/^.*: *//p;}'' | puppet --parseonly --ignoreimport $1 ...but I don''t know the variable to give mercurial; $HG_NODE doesn''t work. Anyone out there using mercurial...? -- Med venlig hilsen Juri Rischel Jensen Fab:IT ApS Vesterbrogade 50 DK-1620 København Tlf: 70 202 407 / Fax: 33 313 640 www.fab-it.dk / juri@...

Hi all, I''m having trouble with a particular recipe, but I don''t know which one! I''m not getting an error message, puppetd simply hangs (does not respond, needs a kill -9 to stop). These same recipes work correctly on other nodes (no problems there). Now I wanted to find the exact line that causes the problem, but I seem to be unable to make puppetd log the resource

Hi, I am working on some tools that read and write pp files, and I wonder if there are some pp files available somewhere that can be used to test a parser. I am especially interested in if there are some tests written that capture invalid syntax. - henrik -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send

Hi All, sorry if this was discussed before but I didn''t find any solution for my problem. Test site.pp consists of 1 line: file { "/tmp/bar": audit => content } exec { ''/usr/bin/true'': refreshonly => true, subscribe => File[''/tmp/bar''] } and it produces this error every time: err: /Stage[main]//Node[localhost]/File[/tmp/bar]:

Hi, I''m pretty sure I once did some experiments with running puppet wihtout a puppertmasterd - but having a "normal" puppet manifests and modules structure in /etc/puppet. Sadly, I can''t find how to do that anymore. I know I can write plain puppet instructions in a file.pp and run them plainly - but I want the whole config as if it would reside on a server) When I

Hi folks, For the first time since I started playing with puppet I started down the road of using exported resources This was inspired by my reading all of the nagios related recipes that went something along the lines of class nagios { package {nagios: ensure=> latest } service {nagios : ensure => running , enable => true} Nagios_host <<! !>>