Issue #13006 has been updated by Josh Cooper. Description updated
---------------------------------------- Feature #13006: Windows registry provider. https://projects.puppetlabs.com/issues/13006#change-59915 Author: Nigel Kersten Status: Needs More Information Priority: Normal Assignee: Josh Cooper Category: windows Target version: Affected Puppet version: Keywords: windows registry Branch: Overview ====== We've had significant demand from Windows Puppet evaluators for functionality to manage the registry on Windows. This is a common thing Windows sysadmins need to do, expressed desired functionality is to: * Pre-license software * Modify proxy settings * Manage custom application registry settings. For our first release, we are not going to target recursion in the registry. Terminology ======== Note that a registry 'key' is not a key in the traditional associative array sense, as registry keys contain unordered lists of 'value's, each of which is a name/type/value tuple. Keys are more analogous to directories, and the registry value a file. Open Questions ========== * <del>What do we do about subkeys? If we're not doing recursion, do we simply ignore them when retrieving the state of a key?</del> I think it should be the same as for directories (without recursion), to manage a subkey, the subkey must explicitly be specified as a resource. * Is it technically feasible to manage HKU for user profiles that aren't loaded? *Nigel seems to remember this is problematic but could be deluded.* Yes, this definitely doable, you have to load the profile, which requires the same privileges that we do when changing file owner. Required Functionality ============== Managing state of keys in the following hives: * HKEY_LOCAL_MACHINE (HKLM) * HKEY_CLASSES_ROOT (HKCR) * HKEY_USER (HKU) * HKEY_CURRENT_USER (HKCU) * *Does this make sense to manage idempotently given the current user changes?* This really only makes sense when managing registry keys that relate to puppet's ability to function, e.g. http proxy settings to connect to the puppet master. * *See open question around HKU* Managing HKU is preferable because it's not dependent on the user that puppet runs as, and can instead be specified as `user => DOMAIN\name` Design Document =========== <https://docs.google.com/a/puppetlabs.com/document/d/1JHXuTGJgfq5sWC2zDTPQGT4c1IQzczP6sQjpDRqB74A/edit> -- 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.
