Very nice. I think there should be support for "delete". Maybe expand "ensure" parameter with values:
present: create key/value if not there, do nothing if there absent: remove the key - the value param would not be needed force: create key/value if not there, force the value to equal the value param I'm not sure why the parameter "auth_membership" is called that. Would this option let me set or replace one value or an array or dict and not blow away the other values, if it were set to true? If set to false, it would blow away all other array/dict values? Also, will it handle the plists in byhost correctly? Figuring our which plist file to change is half the battle. I know there were some articles in recent MacTech magazines about this topic. Have you read them? This look like it's the beginning of being able to manage MCX items via puppet in a more efficient manner. Awesome. Once it's ready, I can envision a ton of type definition libraries to manage all the common stuff. --- Thanks, Allan Marcus 505-667-5666 On Oct 5, 2009, at 8:52 AM, Carl Caum wrote: > Nigel Kersten and I had previously worked on a plist provider spec > for Mac OS X. Attached is a PDF of the current state. I would > appreciate any input and criticisms. > > > > <Puppet Plist native type spec.pdf> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
