so I'm working on a type for the OS X authorization database at the moment.
These authorization rights look like this:
<key>com.apple.activitymonitor.kill</key>
<dict>
<key>class</key>
<string>user</string>
<key>comment</key>
<string>Used by Activity Monitor to authorize killing processes not
owned by the user.</string>
<key>group</key>
<string>admin</string>
<key>shared</key>
<false/>
<key>timeout</key>
<integer>0</integer>
</dict>
but there are quite a lot of keys, and they can almost all accept
arrays as well as strings.
Anyway, I'm unsure whether I should be doing a provider for this. I
can't think of a generic enough term for what this sort of thing is
that is likely to require different providers for different platforms.
If this is something that is always going to be Mac specific, is there
a problem with doing it all as a Type and not having a Provider at
all?
Is there some benefit other than platform difference abstraction to
having a Provider?
--
Nigel Kersten
Systems Administrator
Tech Lead - MacOps
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
