How about merge_exclusive? It shows we want to merge all known entries in the defined dict/array, but also shows we exclusively want those defined.
On Oct 12, 2009, at 10:58 PM, Crawford Kyle <[email protected]> wrote: > Carl, Nigel, > > Thanks for working on this. It looks great and will be a valuable > addition. > > Sorry for the late reply. I haven't been watching the lists closely > lately. > > I agree that the name auth_membership is probably a poor choice > since auth and membership bring to mind other unrelated topics. > > Here are a few alternative names: > > union > merge > merge_values > exclusive > inclusive > > Kyle > > On Oct 8, 2009, at 12:05 PM, Carl Caum wrote: > >> Sorry it took me so long to reply. >> I don't actually remember why we decided on auth_membership >> exactly. I remember I originally had it as purge but that was >> confusing for obvious reasons. If auth_membership was set to true, >> it would blow away every other entry in that dict/array that was >> not known by puppet. This is outlined in the text of the doc. >> >> On Mon, Oct 5, 2009 at 10:10 AM, Allan Marcus <[email protected]> wrote: >> >> 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 -~----------~----~----~----~------~----~------~--~---
