You can do both.
As an introductory tutorial, have a look at
http://www.kartar.net/2010/02/puppet-types-and-providers-are-easy/
and, more information at http://docs.puppetlabs.com/#extending_puppet
On Sep 9, 1:27 pm, SiD wrote:
> Thanks for your quick answer.
> I've already analysed the code, bu
> 2 - Can I say "install this shellscript and run it once"? How?
>
> 2a - Is there an ISConf-like facility that says "run it until it
> succeeds once"? [ Happy to use Makefiles, but if there's a
> Puppet-supported elegant way of doing it... ]
If the code of the shell script can be minimized to use
Hi,
I wanted to have my puppet client daemons running in the noop=true
mode, and changes could be triggered centrally through puppetrun --
noop false. Also it would be nice in an inverse situation, when client
daemons are running in the default (noop = false) mode and before
testing out a new(smal
If I do
1) puppet --modulepath=/home/abc/puppet/modules
OR
2) puppet --modulepath=/home/abc/puppet/modules --manifest=/home/abc/
puppet/site.pp
(...where site.pp has import "nodes.pp", and nodes.pp has a default
node definition that includes basic modules defined under /home/abc/
puppet/modules
I am experiencing the behavior reported in another bug report (http://
projects.puppetlabs.com/issues/1006) in version 0.25.5, that is:
puppetrun --host xyz.def.com --class apache --debug --trace
gives this:
You must be using LDAP to specify host classes
My puppet.conf looks like this:
[ma
Alright so if I have something like
file {"xyz":
ensure=>directory,
mode=>644
owner=>"abc",
group=>"abc",
recurse=>true,
}
...then all this does is to set the appropriate file permissions for
the subdirectories & files under xyz, but it doesn't change the
