similar to: SVN pre-commit hook

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

Hello! I''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

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

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

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

Hello, I'm setting up AD user logins for centos 7.4 box. I've almost managed to do everything the way I want and the way I think it should be, but I'm missing last piece:   For ssh access I read parts of the https://wiki.samba.org/index.php/OpenSSH_Single_sign-on Most docs recommend using setting in smb.conf: winbind use default domain = no that means that all domain users have

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

Hi all, I''ve just installed puppet in my ubuntu gutsy 7.10 linux using gem: # sudo gem install puppet Then, I made a basic site.pp manifest and following the InstallationGuide I ran: $ sudo puppetmasterd --mkusers Could not configure for running; got 1 failure(s) What error? I managed to get an error message on /var/log/daemon.log Jan 30 16:22:13 acero puppetmasterd[13800]:

On Tue, 31 Oct 2017 22:46:53 +0100 Kacper Wirski via samba <samba at lists.samba.org> wrote: > Hello, > > I'm setting up AD user logins for centos 7.4 box. I've almost managed > to do everything the way I want and the way I think it should be, but > I'm missing last piece: > >   For ssh access I read parts of the >

Hi, i have a SLES 11 SP2 64bit host with three guests: - Windows XP 32 - Ubuntu 12.04 LTS 64bit - SLES 11 SP2 64bit The SLES guest shuts down with the host shutdown. The others not. When i shutdown these two guests with the virt-manager, they shutdown fine. ACPI is activated in virt-manager for both of them. Acpid is running in the Ubuntu Client. When the host shuts down, the two guests get a

hi all, we maintain about 30 puppet managed nodes. the version of the clients is 0.23.0 and 0.23.1. the master is 0.23.0. today we installed a new CentOS 5 node with David Lutterkort''s puppet 0.23.2 rpm. this host is a reinstall of an old FC4 on new hardware. we are getting this error on 0.23.2, never happened before: | Could not retrieve configuration: | Failed to parse template

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, I''ve just built rpm''s for puppet-0.23.1 - since there were a few people who had trouble with the update for 0.23.0 (the change in config files requires a bit of rpm trickery), I decided to be a little more cautious in how I push the new packages. So far, new packages are (or, will be shortly) available in rawhide, Fedora 7 updates-testing, and in my yum repos for