On May 7, 11:04 am, Philip Brown <p...@bolthole.com> wrote:
> On Monday, May 7, 2012 7:01:11 AM UTC-7, jcbollinger wrote:
>
> > user { 'alice':
> > ensure => present,
> > provider => 'nisuser'
> > }
>
> > ensures the /etc/passwd contains the line
>
> > +alice::::::
>
> > Those properties that make sense to override locally are also
> > supported. Unfortunately, I'm not at liberty to share, but I can try
> > to offer advice if you choose to go that way.
>
> Please do.
> I'm interested in basically "the minimum" here :)
> What's the minimum I can get away with supporting?
> I'm thinking of going with something really stupid-dumb like requiring
> username, uid, and gid, and supporting nothing else :)
Well then I've got good news for you: to the best of my knowledge, NIS
does not support overriding UIDs or GIDs (or passwords; these three
always come from the map), so that leaves you with just presence /
absence of the name. Your provider does need to deal with the fact
that other properties can be specified, but you don't need explicit
code for them, and just ignoring them will at least get you off the
ground.
The place to start is probably:
http://docs.puppetlabs.com/guides/custom_types.html.
That will eventually lead you to
http://docs.puppetlabs.com/guides/provider_development.html.
I would recommend also reading
http://docs.puppetlabs.com/guides/complete_resource_example.html.
For my work, I depended most on the second of those three.
You may be able to base your provider on the ParsedFile general-
purpose base provider, though I did not do that with mine.
Don't forget that you will need to support both "ensure => present"
and "ensure => absent", and that you probably want to avoid creating
duplicate records.
That's all the general advice I have at the moment, but if you run
into trouble with specifics of the implementation then there are
several of us around here who can probably help.
For what it's worth, my provider is about 350 lines of Ruby code,
about a third of which are whitespace or comments, and the vast
majority of that is related to prefetching and / or flushing
instances. It should be possible to do a simple-minded version
supporting just present / absent with a lot less code if it doesn't
need to prefetch and flush.
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.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
