search for: metaparams

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

...quot;: ... } looks like a regular type, > and people don''t expect the require parameter > to be dropped silently in _some_ cases, which is what happens now. I wonder if you could have a new, fresh, more favourable look at #446 now that I submitted a patch? It does make relational metaparams work differently, but I really do think this way is more intuitive... -- Marcin Owsiany Web Systems Integrator - Guardian Unlimited ------------------------------------------------------------------ The Guardian Public Services Awards 2007, in partnership with Hays Public Services, recognise an...

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

When you use alias in a definition or class ie. Access alias fom within the same enclosing scope you created the object that provieds the alias in it wors fine. I use alias in that exact case frequently eg. For requirements/subscribes etc. ----- Urspr?ngliche Nachricht ----- Von: Francois Deppierraz <francois at ctrlaltdel.ch> Gesendet: Dienstag, 28. August 2007 19:19 An: Puppet User

Hi, Since upgrading from 0.24 to 0.25, I''ve seen repeatedly puppetd clients just stop when they''re unable to reach the puppetmaster for a while. With the normal logging level, they just seem to stop without writing anything in their log. I''ve seen this with 0.25.1rc1, rc2 and final, which are all of the 0.25.x I''ve tried (always with the same version on

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

....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.rb...

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",

Hello, I am running a puppet master version 2.7.5 on Centos 5.7 and a puppet agent version 2.7.5. I am simply trying to apply changes to files by defining a file resource in my manifest. When I execute my puppet agent to do the installation it complains it can not find the file meta data. Here is my manifest. class neospeech::config { file { "/usr/vwmrcpd/vwmrcpd/vwmrcpd":