search for: metaparam

Hi, I''ve got the following resource: host { "host.domain.com": alias => [ "host", "alias" ], ip => "1.2.3.4", ensure => present, } The resulting line in my /etc/hosts file is: 1.2.3.4 host.domain.com Any alias definitions seem to be ignored? What am I doing wrong? Best regards, Dieter -- You received this message because

Hi, I have this code here: $filepackages = $operatingsystem ? { debian => [ "tar", "gzip", "bzip2", "diff", "sed", "wget" ], default => [ "tar", "gzip", "bzip2", "diff", "sed", "wget" ] } package { $filepackages: ensure => latest

On Thu, Jun 28, 2007 at 10:24:42AM -0000, puppet wrote: > #446: Require should stack not override [...] > Comment: > > Here is a patch against 0.23.0 which I think fixes this. It essentially > makes all relationship metaparameters stack up, rather than get overriden. > > --- puppet-0.23.0.orig/lib/puppet/parser/resource.rb 2007-06-17 [...] > > I strongly feel that without this feature, definitions don''t work as > people expect them to. > In the original report, alpha { "Wobble&qu...

Is the host_aliases parameter to sshkey new in 0.25? Jun 1 15:28:48 s_sys@ext3.fr.xxx.com puppetd[20358]: Could not retrieve catalog: Invalid parameter ''host_aliases'' for type ''Sshkey'' at /etc/puppet/manifests/nodes/fr.twofish.com/ext3.pp:19 on node ext3.fr.xxx.com Jun 1 15:28:48 s_sys@ext3.fr.xxx.com puppetd[20358]: Not using cache on failed catalog The

Hi folks, I''m overriding some resource attribute in a subclass. It seems that specifying a resource by its alias doesn''t work in a subclass. Looks like a bug, no ? === module-classes.pp === class module::base { file {"/tmp/test-module": alias => test-module, content => "module::base", } } class

We have resources that, from time to time, are selected to be removed (unmanaged). When it comes to ssh keys, fstab... this leaves a lot of stuff behind that we don''t want. Is there a simple way to remove the unmanaged data so we can keep the systems clean. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

...Nachricht ----- Von: Francois Deppierraz <francois at ctrlaltdel.ch> Gesendet: Dienstag, 28. August 2007 19:19 An: Puppet User Discussion <puppet-users at madstop.com> Betreff: Re: [Puppet-users] Aliases not working in a subclass ? Luke Kanies wrote: > The ''alias'' metaparam is only used on the client, which means that > the parser doesn''t know anything about it. I can''t decide if this is > a bug or not, considering that you''ve already got the ability to > easily have two names for your resource (the name and title). Thanks, everyt...

...ients stop in a similar way. Here are the relevant lines of the puppetmaster.log : Sun Nov 01 04:02:05 +0100 2009 Puppet (notice): Reopening log files Sun Nov 01 04:02:05 +0100 2009 Puppet (notice): Starting Puppet server version 0.25.1 Sun Nov 01 04:02:16 +0100 2009 Puppet (warning): require is a metaparam; this value will inherit to all contained resources Sun Nov 01 04:17:33 +0100 2009 Puppet (warning): ''newservice'' method already exists; skipping Sun Nov 01 04:18:42 +0100 2009 Puppet (notice): Compiled catalog for foo in 992.54 seconds Sun Nov 01 04:18:58 +0100 2009 Puppet (notic...

Following patch for pfile.rb and pfile/source.rb allows the user to set a replace => false parameter on a file sourced by puppet, but not replaced if checksums do not match. This is for cases in which it is desired to distribute initial "bootstrap" files and ensure future existence, yet allow them to be modified on the node. RTS --- pfile.rb~ Wed Aug 2 04:47:05 2006 +++ pfile.rb

A little while back I asked how to make puppet not report on a resource.. and was shown the loglevel metaparam: Quoting bellman@nsc.liu.se: There is a metaparameter called ''loglevel''. If you set that to something lower than "notice" (i.e. either "info" or "debug"), then Puppet won''t report that it applied the resource... So I made my resource like...

....rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/container.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/evaluation.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/instances.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/manager.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/metaparams.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/providers.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/relationships.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/schedules.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metatype/tags.rb ./opt/csw/lib/ruby/site_ruby/1.8/puppet/metric.r...

Hello, I want a simple operation in a puppet node like restarting the ssh service if it was stopped. My site.pp is simple as this: import "services/*" node default { include ssh } The services directory as a ssh.pp : class ssh { service { ssh: ensure => running, subscribe => File["/etc/ssh/sshd_config"] } } I''ve stopped the ssh service in the

I constantly get told I should just create a DSL in Ruby, instead of having a separate, custom language. This has, unsurprisingly, come up multiple times here at OSCON. So, I decided I''d see if I could hack something up and see how it looked. This is the first thing I could come up with in terms of the basic functionality: #!/usr/bin/ruby class Base file "/etc/passwd",

...; in environment production debug: importing ''/etc/puppet/modules/rvm/manifests/classes/ dependencies.pp'' in environment production debug: importing ''/etc/puppet/modules/rvm/manifests/classes/passenger- centos-pre.pp'' in environment production warning: stage is a metaparam; this value will inherit to all contained resources debug: importing ''/etc/puppet/modules/rvm/manifests/definitions/ system_user.pp'' in environment production debug: importing ''/etc/puppet/modules/ldap/manifests/init.pp'' in environment production debug: Automatic...