similar to: testing static manifests

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

Hi All, Am new to puppet and started writing simple manifest files. I have setup Server/Client mode for puppet and when I try to apply my manifest to local machine using "puppet agent" everything works well. Is there any option to apply the manifests to a remote machine without ssh into the machine? -- You received this message because you are subscribed to the Google Groups

Hi there, I''m running puppetmasterd manually while testing, and I was trying to split my manifest in several parts using import. If I do so whenever I run the puppetmasterd the manifest gets loaded and served correctly: cognos ~ # puppetmasterd -v info: Starting server for Puppet version 0.20.0 info: Parsed manifest in 0.02 seconds info: /var/lib/puppet/files: allowing *.example.org

Hi, I''d like to announce a little tool I have written, called cucumber- puppet. It supports writing behavioural tests for your puppet manifest, using cucumber. This allows for BDD-style manifest development and fearless refactorings. http://blog.nistu.de/cucumber_puppet_0_0_3_released.html Let me know what you think! cheers, Nikolay -- You received this message because you are

Hi there, I''m trying to document my puppet manifests, and I have created kind of a template for class documentation. After documenting a few I thought it would be great for complex manifests if we could have a tool that read some kind of standard documentation in puppet manifests and create HTML (or other format) documentation, as javadoc in Java or RDoc (?) in Ruby. So two questions:

I am trying to figure out if I am missing something simple here. After upgrading to puppet 3.0 running puppet-rspec tests that use custom resources from modules in the fixtures directory are failing. I have a module that uses the anchor type and with 2.7.19 it works fine. After upgrading to 3.0 all of the tests are failing with Puppet::Error: Puppet::Parser::AST::Resource failed with

Hi As I''m more familiar with cfengine and it''s way to split updates (in update.conf) from the actual grunt work (in cfagent.conf), I''m wondering how to best manage puppet and my manifests with puppet...? Should I define a puppet class that copy the puppet package (in .tgz format) and all the manifests to the client, and then have all my other classes depend on

Puppet 3.1 is released, but problem not fixed. Puppet 3.0 and 2.x don''t test manifest for non-ASCII and write uncorrect characters to system (like file names, folders, files and other) . But now Puppet 3.1 test manifest and stop.<https://lh5.googleusercontent.com/-aRLPbc_OYbA/UQY4w9ivc6I/AAAAAAAAACU/nqH8b5IRbgI/s1600/puppet%2B3.1b2.png> -- You received this message because you

There''s definitely enough complexity in some of the modules out there to warrant solid test coverage, especially if people start extending a module to support more distributions and OSes, while trying to keep the existing support working. That''s even before you start thinking about functions, facts, and native types. They''re *really* in need of solid testing, being all

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

I try do implement tests for my puppet code and was playing with rspec-puppet but the following code gives me errors require ''spec_helper'' describe ''irqbalance'' do it { should include_class(''irqbalance'') } it { should include_class(''irqbalance::data'') } it { should

Greetings all Am trying to solve a problem, not entirely sure I''m approaching it from the right angle. Setting up a reasonably big site (servercount in the four digits) with puppetmaster and clients (puppet 2.6.x). We are required to have versioned modules (base SOE module, app X module, app Y module, etc - all with multiple classes etc inside) managed on an underlying SVN repository. A

Anyone ever thought of making the service type in puppet able to deploy new services? I''m not sure this would be useful for all OSes, since package management systems generally install init scripts. Well it''d still be useful for Linux if you''re managing any customized services. For Solaris, it''d be great if I could just give puppet an SMF XML file, and say

Trying to understand how puppet reports errors Example of why I am asking the question (on a test setup environment) Created a base-1 node Created 2 slave nodes that inherit from base-1 Let''s call those slave1 and slave2 No errors. It all works. Created a base-2 node created a third slave that inherits from base-2. Let''s call that slave3 Get an error Could not retrieve

We are in the process of evaluating our puppet related test and release process and interested in knowing what other folks are doing. We are in a position that is not ideal but is not unique from what I can tell. Our current testing process is basically the responsibility of each person making a change. Small changes are committed and pushed to dev/qa/prod in one swoop with the committer spot

I recently started trying to use rspec-puppet and puppetlabs-rspec-helper. When I ran ''rspec-puppet-init'' in one o fmy modules, it created a series of symlinks. Now, when I run puppet doc (via a rake task supplied by The Foreman, but also when I call it directly) I get the following error: Could not generate documentation: Definition ''mongodb::addmongouser''

I created manifest for our webserver. manifest included git clone, database creation and restore database etc.... How to order the installation and exec exactly Roni -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to

Hi List, Puppet Version: v2.7.13 Question - If I correctly setup multiple manifestdir''s in the puppet.conf file how can I import a node pp file located in a different directory tree to site.pp? My configuration information is below. In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and

Hi, I was talking to Luke today about managing manifests and related files, and he suggested that I post to the list.. What would be nice (and what I''ve use in in-house systems I''ve used previously) is to have a way to dynamically include manifest fragments at runtime. Lets assume that you''re setting up bugzilla using puppet. In the ''main'' manifest

I also made the changes below in the puppet.conf file to tell puppet where to look for the the modules and manifests. I then restart the puppet master then ran puppet command to apply changes to a puppet client it did not find anything to change just got these three lines "info: Caching catalog for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version