On Saturday, January 26, 2013 6:55:57 PM UTC-6, Matthew Pounsett wrote:
>
> I'm trying to extend the standard 'user' type to add maintenance of some
> of the contents of a user's home directory, and I'm trying to avoid
> creating an entirely new custom type if I can. The approach I'm taking is
> to create a site::user defined type which in turns calls the standard user
> type.
That's a good and widely-used approach.
> I'm having a problem figuring out how to manage the optional parameters.
>
> The most likely path seems to be something like this (simplified for
> example):
>
> define site::user (
> $comment,
> $ensure,
> $home,
> $name = $title,
>
Don't do that ($name = $title). Puppet provides it automatically (both the
parameter and the default).
Moreover, I am uncertain whether it is safe anyway to use $title as a
resource default. It certainly *isn't* safe to use explicit resource
properties, regardless of the order in which they are listed.
> $password,
> ) {
>
> user { "$title":
> comment => $comment,
> ensure => $ensure,
> home => $home,
> name => $name,
> password => $password,
> }
> }
>
> The problem with this, of course, is that the parameters to site::user
> aren't optional, and I'd like them to be. I've tried setting their
> defaults to null strings, but I get errors about reassigning variables if I
> do that.
>
The usual paradigm is this:
define mymodule::foo ( $param1 = 'NOTSET' ) {
$real_param1 = $param1 ? {
'NOTSET' => <some-appropriate-value-maybe-undef>,
default => $param1
}
sometype { $name:
param => $real_param1
}
}
Yes, it's a bit clunky, but it works.
> Of course, this would be even better.. but doesn't appear to be a valid
> syntax in puppet:
>
> define site::user ( $**args ) {
> user { "$title":
> $args
> }
> }
>
>
No, Puppet doesn't have anything like that. The closest would probably be
the create_resources() function, which you can read about in the docs.
> This seems to me to be the sort of thing that'd be in a puppet cookbook,
> but google hasn't shown me any useful docs or examples for what I'm trying
> to do. Does this approach even make sense, or is there a better way?
>
I'm surprised you didn't find an example like the one above. It appears
all over the place, not least in the archives of this group.
Also, have you read the official Puppet DSL docs (at
http://docs.puppetlabs.com/puppet/3/reference/)? They don't answer your
particular question, but they would have told you about $name, and they
have a lot of other useful information.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
