similar to: Puppet Forge question

Is there a way to get a list of all the classes available from the puppet master? I have 2 goals for this - one is documentation in a human readable form, and the other is potentially importing that data into dashboard. I did find some info on the rest API (http://docs.puppetlabs.com/guides/rest_api.html#resource-types ) but I can''t make any sense of the output from it. Thanks.

I have a module located at /etc/puppet/environments/test/modules/ruby. I n this I have a manifests folder with two .pp files - init.pp and gemInstall.pp. In one of my node def files I have: include ruby ruby::gemInstall { ''someGem-version.gem'': path => ''/path/to/agent/local/gem/repo'', } ruby::gemInstall is a define, and it has some logic to get around

Hi all We''ve just released version 0.3.4 of the puppet-module tool used to create and retrieve modules from the Puppet Labs Forge (http://forge.puppetlabs.com). You can update using Ruby gems: $ gem install puppet-module There are several important changes in this release: * Add ability to install modules with hyphens * Add check for symlink when installing * Install modules to their

Hello all, I have some questions about the download puppet modules from puppetforge: I''ll take puppetlabs-dism as an example, once its installed its located: /etc/puppetlabs/puppet/modules/dism Can this be renamed to something else ? Also if for example, I had a folder tree under modules e.g. /etc/puppetlabs/puppet/modules/windows | |- manifests |--base.pp |--networking.pp Can I

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

Does puppet doc require a specific version of any gems (such as rdoc or rake) to operate? I''m getting some errors when I try to generate my rdoc now. # puppet doc --output /var/www/test --modulepath /etc/puppet/environments/test/modules -m rdoc RDoc::RDocError is deprecated and will be removed in RDoc 4 Could not generate documentation: uninitialized constant RDoc::RDoc::Generator

I´m trying to utilize the new stdlib module, but got stuck after installation on my puppet server. I´ve tried to use the included test file file_line.pp on the server, but it´s only creating the file - but not managing the content. the same problem on my clients (the new provider file_line has been synced), it´s just not working: file_line { ''puppet master host

Hi. I want to run script which is distributed with my module, but the problem is I have to then hardcode the path to the script in the generate function call, for example: generate("/etc/puppet/environments/${environment}/modules/mymodule/scripts/myscript") But what If some other site uses other path to their modules, or doesn''t use environments at all? Is it possible

I''m setting up a dev / test environment using a couple of Ubuntu 12.04 VMs. I have puppet installed on one of them, and am trying to get it to sync against itself to get certain things in place to distribute with the nodes. However, I am having some issues. # puppet agent --test info: Creating a new SSL key for puppet-local-master err: Could not request certificate: getaddrinfo: Name

Hi, I wonder why the puppet agent on the server itself will not run: ---snip--- # puppet agent --test Error: Could not run Puppet configuration client: Puppet::Node does not respond to from_s; can not intern instances from text/plain Error: Could not run: can''t convert Puppet::Util::Log into Integer ---pins--- whereas the client on a test box tells me: ---snip--- # puppet agent --test

I want to setup a node using a three step process 1) download node requirements (git) 2) download modules to fit requirements (puppet) 3) Bring up the node in the required state (puppet) The second step is the one I am having trouble with. I want a file (master.pp) to list out all the modules and what versions are needed before applying the site.pp file. From what I have been able to find

Hi... I''ve been trying to set up boolean values in Hiera, but with no luck. For example, I''m using puppetlabs-haproxy module, and this is a code snippet: class haproxy ( $manage_service = true, ... ) inherits haproxy::params { ... if $manage_service { } } Now, this is how I set up values in hiera: haproxy::manage_service: false But, it seems that

Currently and going forward people will be running multiple versions of puppet. What are the plans for puppet compatibility with Modules? Thinking we may want to be able to specify what version of Puppet is running and ask for the compatible module. (Which may be the same). Thanks, Brian -- You received this message because you are subscribed to the Google Groups "Puppet Users"

Hi, I have been working on a new puppet code formatter for Geppetto for some time, and it is now starting to work quite well. The plan is to release it in Geppetto 3.0. If you want to, you can help by sending "formatting puzzles" - i.e. "given input x, produce formatted result y". I am esp. looking for code where it is impossible to follow "the style guide" -

Hello, If you weren''t at PuppetConf or didn''t catch my talk, here''s a quick recap. I''m product owner for the Puppet Forge team which formed in July with 2 awesome engineers and an equally awesome designer. We''re a team dedicated to the Forge and while ramping up, we''ve shipped three small improvements to the Forge that we hope you enjoy. *

Hi, Puppet 3.1 now uses YARD to generate its API documentation. Is anybody aware of the possibility to generate nice YARD docs for a given module path, replacing the default RDOC-style site from "puppet doc --modulepath ..."? Could the YARD Template from Puppet 3.1 be used for this? -- You received this message because you are subscribed to the Google Groups "Puppet Users"

Hi group, im updating some modules of puppet, and i found this issue or error, that i cannot get resolved it. My puppetmaster is 2.7.1 and client 2.7.18. I used other modulo to prover apt configurations but i think this is more completed. I know that the error is something missing or my class is not present or something like that, the dependencies of the modulo are installed, stdlib and i

Hi, I''ve been trying to pass the http_proxy_host option to puppet but it''s not taking. I have tried the following: sudo puppet apply --debug --verbose --http_proxy_host http://user:pass@fqdn.com.au --modulepath ''/tmp/vagrant-puppet/modules-0'' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose

Hi, I bumped into the following this afternoon (on a 2.7.19 puppet master/agent combo): consider a class profile::tomcat in module profile with the following content: $ cat modules/profile/manifests/tomcat.pp class profile::tomcat { class { ''tomcat'': } notice(''Class profile::tomcat in module profile'') } and $ cat modules/tomcat/manifests/init.pp

I''m in the process of refactoring some code and getting it ready for 3.0 in the process. I''m trying to better modularize things as well. I''ve got a general tomcat module, but I also have a number of tomcat related things that only apply to one class of appserver we have. What would be the best way of handling these? Should I create a module, say, teamname_tomcat