search for: puppetdir

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,...

...ire => Exec["clone-repo-${name}"], } } } } } Then I call it like this: (for my puppetmaster in this case) git::repo { $puppet_modules: src => "${gitserver}", dst => "${puppetdir}/modules/main/", use_names => true, } where: $puppet_modules = [ ''puppet'', ''ssh'', ''apache'', ... ] # and so on listing out all my modules This works great, no problems, in my yaml I can define a list of modules th...

There was a discussion a while ago about adding inheritance to definitions. There is a need for a way to specialize parameters while allowing passing other options. This comes up with remotefile where it would be nice to have a default server location but not specify all the parameters (and their defaults) in the definition. Was there a change to the syntax? Is there a way to accomplish this?

Hello, I''m writing my first puppet function rspec test and am having a problem which I don''t see how to solve. The function (and the test) involve access to files through the File Server. In order for the function (and the test) to work I need to pass "--fileserverconf=fileserver.conf" parameter to Puppet. So far I haven''t found a way to do that. If I

I have the following define... define puppet::module_dir { if $name { include puppet file { "${puppetdir}/modules/${name}": ensure => directory, mode => 0755, purge => true, recurse => true, } } } I call it like so: puppet::module_dir { "main" } puppet::module_dir { "dev" } ... the...