similar to: possible parseonly behaviour changes

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

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, Is there maybe an undocumented parameter with which to tell puppet to create missing parent directories when using the ''file'' type? And if not, should there be? I actually expected it to be default behaviour to create missing parent directories when doing something like: {{{ file { "/usr/local/svn/repos": ensure => directory, owner => root } }}}

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site:

I''m using the external_nodes functionality to read in a flat file of a node''s configuration. Currently said file is a straight yaml file (just to keep things simple). The place I''m currently stuck is in doing some more advance node configurations and placing that data in the yaml file. For example: node ''foo'' { $var1 =

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

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 all, When making changes to the wiki, please make sure to add a comment describing your change -- it makes it far easier to read the RSS feed or the timeline. Digant is being a diligent doc wrangler, but he needs your help managing the changes over time. Also, if you''re making many (or maybe even any) modifications to the wiki, please make sure your profile is configured

Hi all, I''ve now finished all of the functionality I plan to add in the next release, so all that remains is closing as many open bugs as possible. I''ve gone through and marked all of the bugs I specifically plan on fixing with the ''minor'' milestone. If you have a bug in the db[1] that you think needs to be fixed in the next release but is not

So, I just looked into how I handle this internally. By default, the server uses the hostname contained in the HTTP request. If this name disagrees with the hostname in the certificate, then the certificate name is used. This is the hostname passed to all XMLRPC calls. Most XMLRPC calls don''t include facts, so I can''t use the facter-derived hostname except for in the

Hi all, This has theoretically been a high priority for a long time, and I''m finally going to get it done, I think. Here''s my plan, and I''d appreciate any comments you might have on it. Currently, sections only have meaning internally, in that one can call ''config.use(section)'' to create any directories needed for that section. Additionally,

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

Ok, so I''m obviously doing something wrong here. This is running puppet 0.22.2 on a centos 4 update 4 box. When I try running this test - mount { bigdisk: ensure => mounted, device => ''bigserver:/bigdisk'', fstype => nfs, name => ''/bigdisk'', dump => "0", pass => "0", options =>

(I''m emailing the list, rather than direct.) Adnet Ghislain wrote: > Hello, > > More on my deployment, i have an issue where the fact sometime does > not load and it seems that they do not work and as i rely on facts in it > ll fails: > > Oct 6 02:54:18 oiseadmin puppetd[42243]: Could not call > fileserver.list: #<Errno::ECONNRESET: Connection reset

Hi all, Turns out there''s a small backward compatibility problem in 0.22.2. If you''ve got clients in older versions sending reports to a daemon running the newer version, you''ll run into a problem because I renamed the Puppet::Metric class to Puppet::Util::Metric. I''ve committed a fix to svn, but it''s not a big enough problem to require a new

Hi, I think I''m having a similar problem to the user who raised this bug: http://reductivelabs.com/trac/puppet/ticket/733 I''m running 0.23.2 with storeconfigs. I''ve got it working to the point where my clients'' facts are being populated in the database[*] but updates don''t seem to happen unless I restart puppetmasterd. For example: 1) I run my test

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

Here at the University of Sydney I''m trying to give Puppet a go. I haven''t made it past first base yet unfortunately. We run RHEL 4 here, for the most part, and the install guide at http://reductivelabs.com/trac/puppet/wiki/InstallationGuide says that you should use the vendor''s Ruby, but Red Hat''s current version of Ruby is 1.8.1-07 - is this new

There was an old email thread from the end of January 2006 discussing regular expressions for matching URLs. I took some of the sample expressions and tweaked them a bit to the point where I think they are pretty useful. They pass all of my tests anyway. :-) For a reminder, here''s a sample message from that thread. My code is below it. On Jan 26, 2006, at 5:28 AM, Nathaniel S.