The overhead of explicity realising the resources would be too great.
Specifically what I am trying to achive is disabling accounts on existing
hosts, while preventing them from being created when new hosts are turned
up. So when a user leaves the company the account would be disabled by
lockin
Use a virtual resource ?
It will not be created unless you explicitly realize it.
You can centrally manage a collection of virtual users on your Puppet Master,
creating only those you want on the nodes you want them on.
Does that satisfy your requirement ?
“Sometimes I think the surest sign tha
I'm on Centos 5 - which I assume would behave the same as Fedora. From my
testing it would seem that the default behaviour for user type is to create
if absent. I tried looking at the Puppet source to see if this behaviour
can be easily modified, but as someone who doesn't know Ruby I couldn't g
On Fedora the behaviour between types is different. A file resource is
not created if it doesn't exist:
notice: Finished catalog run in 0.08 seconds
biguml@biguml-laptop:~$ ls -ld /tmp/woof
ls: cannot access /tmp/woof: No such file or directory
biguml@biguml-laptop:~$ cat test.pp
file { '/tmp/w
Hi Alan,
What OS / provider? At first guess I'd say it's a side affect of the
commands the provider is using to change user attributes (useradd
instead of usermod?). If you run puppet with --debug you might get
output from the provider to see what it's doing.
-Luke
On 31/05/12 17:25, Griffa
