Issue #1606 has been updated by zanzamer.
I think most LDAP servers will not handle "transactions" on data, instead (if it support versioning) it will save versions of particular attributes. Maybe puppet should use this feature of LDAP servers to save groups of changes as versions... (I mean particular on AD, I don't know of advanced versioning feature in AD, maybe it will be helpful..) ---------------------------------------- Feature #1606: Versioning, history and merging configuration saves on LDAP servers http://projects.reductivelabs.com/issues/show/1606 Author: zanzamer Status: Needs more information Priority: Normal Assigned to: Category: LDAP Target version: unplanned Complexity: Unknown Affected version: 0.24.4 Keywords: Hi, I saw puppet is highly suggested to be used with version tracking and managing software such as SVN or CVS, in order to easily manage changes. On the other hands, I'm a tough supporter of defining "Nodes" by Distinguish Name in LDAP or AD Domain, in order not to "inventing the wheel", and store puppet configuration in LDAP server as well (automatic replication, site management and scalability and so on). I think combining both features will add a great added value to Puppet, comparing to other products. Will puppet support versioning of LDAP configuration? (this is technical possible). Please update me in [EMAIL PROTECTED] ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
