similar to: Problem with syntax checking

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

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

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

Hi i am creating a template.pp for different OS.. Following is my template.pp file node basenode { case $operatingsystem { fedora: { include fedora } default: { 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

Hi is anybody using the svn pre-commit hook from http://www.reductivelabs.com/trac/puppet/wiki/VersionControlPuppet with 0.24.1 . It was working fine with 0.23.1 and I like it to test stupid typos before checking in. However after updating to 0.24.1 I get the following error for the site.pp: Could not parse for environment development: No file(s) found for import of

Hi all I''ve watched all the discussion about svn commit hooks, as I really want to integrate that into my system - the only thing is, that I use 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

We have started having developers make changes to our manifests file. We have a couple of changes with errors that have broken updating for all clients. We even ran into a bug where a broken configuration on puppetmaster start would cause it to return 500 server errors to all clients. I would like to have a way for developers to check their changes before committing them to version control and

I don''t manage any macosx machines but I do run puppet standalone 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

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 difficult and more ambiguous when used with

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

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

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

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

Hi all, I think the 0.23.3 release is ready, with this changelog: Pulling the code related to the fixes for #896 from the 0.24.x branch. This provides support and workarounds for the security fix in Ruby that requires the server certificate naem to match the name the client is connecting to. Applied a few small fixes from the current 0.23.2 Debian package:

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 <<! !>>