Sure. My mistake came from thinking that a class whose resources all had
variable titles, like file { /path/$varname:, could be called multiple
times as long as each call had a unique value for the variable. Once that
bit was sorted I wrote my users type nearly identically to Keiran's
example.
I'm sorry for the late reply. I've been on holiday. Your suggestion was
exactly what I needed and has helped me in more ways than just the users
module. Thank you so much!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion
J slavetonagios:
Can you give the group more detail about how it helped you?
Stuart
On Dec 30, 2012, at 6:36 PM, j slavetonag...@gmail.com wrote:
I'm sorry for the late reply. I've been on holiday. Your suggestion was
exactly what I needed and has helped me in more ways than just the users
Hi There,
Thanks for the additional information it actually helps me understand what
you are trying to achieve a bit better.
As per the types documentation, this line is quite important to understand:
Classes are good for modelling singleton aspects of a system, but to model
repeatable chunks
Hi,
I have found when working with user accounts it is very beneficial to
create a defined type that allows you to wrap alot of functionality into
one definition, thus reducing manual work and being more explicit with your
requirements for user data and account configuration when they are
Thank you for the reply, however I do not see where that resolves the
dependency problem. Let me paste what I've been playing with as maybe that
will clarify my problem:
class admins($username, $ensure='present') {
if $ensure == 'present' {
$dirensure = 'directory'
}
elsif $ensure ==
