similar to: $environment in File source not working

Is it normal that "facter --puppet" does not show the environment variable? is there a way to have it include it? Thanks a lot, Mohamed. -- 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

Hello all, This is not a puppet proper issue of course.. but I was wondering if any of you could share some thoughts... When you deploy a system like Puppet at a large park of systems, you instantly increase the efficacy of mistakes and bugs in destroying the environment.... How do you deal with that? I would be interested in any experience or input, especially puppet proper best practices...

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

My custom external nodes script sets the environment variable, but Puppet ignores it. For testing, I have a manifest that deploys this template to a file: environment = <%= environment %> The output from my external nodes script: --- classes: - devhost environment: development parameters: memcached_memory: ''32'' But running "puppetd --test" results in the

Hi all, I am using puppet with an ENC script. In this scripts YAML output the environment (generally "production") is set. For testing purposes I would like to start puppet runs from the cmdline of a managed host like: $ puppet agent --onetime --no-daemonize --verbose --no-splay --environment development The problem is the --environment Parameter is not being used if an environment

The file{} type can do all of the following: * manage single files * manage directories * manage symlinks * manage recursive file copies The intersection of all these bits of functionality makes it difficult to understand exactly what is going on when you''re new to Puppet, and even experienced users often don''t know how combining symlinks/content management is going to work.

so here are my unorganized thoughts on Passenger settings. * PassengerMaxPoolSize This depends a lot on two primary variables. a) How much RAM you have. b) How much resident memory is needed for your environments/modules. Only way to determine this is with tweaking, and you''ll need to be much more conservative than the suggested settings on the Passenger docs as your app takes up a lot

I''m looking at re-working or replacing install.rb from the source distribution to allow more flexible installations, primarily to get MacPorts and Fink packages working but to also work on automatic Mac pkg creation from source. How are people currently using it? Currently the command line options are for options like --no-rdoc, --no-man, --quick, --full, but if you want to specify a

Do I remember correctly that puppet-forge is no longer accepting uploads? -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- 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

user {''username'': uid => 501, gid => ''staff'', comment => ''comment'', ensure => present, home => ''/Users/sysop'', shell =>

Seeing ''SSL_read'' errors being logged by puppetmaster. Anyone know what causes these or how to correct? They''re sporadic, not happening all the time or on all puppet runs. /var/log/puppet/masterhttp.log [2011-07-25 10:00:10] ERROR OpenSSL::SSL::SSLError: SSL_read:: internal error /var/log/messages Jul 25 10:00:10 cmd-box puppet-master[22572]: SSL_read:: internal error

0.25.5 changed the default vardir from /var/puppet to /var/lib/puppet and it''s caused the odd issue we have to fix in the Mac pkg preflights. After re-reading ''man hier'' I''m tempted to change the default on OS X to: /var/db/puppet instead. /var/ multi-purpose log, temporary, transient, and spool files ...

Reminder for Mac Puppeteers going to WWDC How about we meet for lunch at noon on Tuesday. Let''s try to get the table closet to the Odwalla refrigerator, just for reference. We can get more specific on this list on the 8th after we verify the set up. I might even get there a little earlier and put down "reserved" tags. --- Thank you, Allan Marcus Solutions Architect Central

So I can''t quite see how to do this in the existing syntax. Ideally there would be an onlyif parameter for packages, but that doesn''t seem to be the case. I could create a fact that returns true or false depending on whether the file exists, but that doesn''t feel like the right way to do it either. I could do something like: $file_exists =

Hi, Why doesn''t puppet resource group tell me who belongs to the group? Given the group such as: mg_team:x:501:smruph, cosman, msmith, mhankey With the command: puppet resource group mg_team only returns: group { ''mg_team'': gid => ''501'', ensure => ''present'' } I was expecting: group { ''mg_team'':

So we run puppetd as a long running ruby process on the hosts. When we update a fact that gets auto sync''d to the host it seems when puppetd wakes up and starts its catalog run it doesn''t re-sync the facts. It you run it standalone it will or if you restart the service then it will do the right thing. Do other people see this? Or have you all gone to running out of cron?

C:\Users\ml623>puppet --version 2.7.7 Puppet complains about a package resource I am trying to use saying: Invalid parameter install_options The resource is defined as: package { "splunk": name => $gu_splunk::client::splunk_package, provider => ''msi'', ensure => installed, source =>

I''m new to Puppet, and I''m a software developer, not a sysadmin, so be gentle. I have puppet managing some files via templates, and one of the template variables that needs to be plugged in is a password of sorts that shouldn''t be generally available. In particular, it can''t be stored in the manifest, as that''s stored in version control, and the

packages.debian.org is lagging in terms of what it''s showing, but.... $ rmadison -u debian {puppet,facter} | grep unstable puppet | 0.25.4-1 | unstable | source, all facter | 1.5.7-1 | unstable | source, all they''re both up there now. -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

I want to manage cronjobs as a " file " in solaris through puppet and not using the puppet cron resource. I will be managing the file /var/spool/cron/crontabs/root. I want the cron file to be same across all servers except some servers will have additional cron entries. How can I append to the file /var/spool/cron/crontabs/root , something like appendifnosuchline in cfengine? Can