Issue #1606 has been updated by Nigel Kersten. Status changed from Needs more information to Closed Assignee set to Nigel Kersten
As per the below thread, we're more aggressively closing tickets whose state is unsure, particularly old tickets with little to no inactivity in a long time. You are free to reopen them. http://groups.google.com/group/puppet-users/browse_thread/thread/a040cb9bc5c5b647 ---------------------------------------- Feature #1606: Versioning, history and merging configuration saves on LDAP servers https://projects.puppetlabs.com/issues/1606 Author: zan zan Status: Closed Priority: Normal Assignee: Nigel Kersten Category: LDAP Target version: unplanned Affected Puppet version: 0.24.4 Keywords: Branch: 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://projects.puppetlabs.com/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.
