Hi Jeff, On Mon, Aug 20, 2012 at 11:43 AM, Jeff Sussna <j...@ingineering.it> wrote: > OK, I got registry::value working by commenting out the calls to > validate_re. I will file a ticket for that.
The registry module has a dependency on the stdlib module. When installing the module on a unix puppet master, the dependency will be resolved automatically (stdlib module will be downloaded if necessary). And since the running the module tool on Windows is not currently supported (in large part because of the tar.gz format, see [1]), you'll have to manually download the stdlib module to your Windows box. > Unfortunately, though, the > Windows gotchas continue. If you manually edit PATH in the System control > panel, the new value shows up the next time you open a new cmd window. If, > however, you edit it in the registry, the change doesn't show up until you > reboot the machine. I've verified this behavior in XP and Server 2003. I found this post: http://mnaoumov.wordpress.com/2012/07/24/powershell-add-directory-to-environment-path-variable/ Broadcast to all windows that the environment has changed. > I also discovered an "inconvenience" with the puppet registry module. > registry::value calls registry_value, which appends the value to the key to > create a namevar. That means you can't edit PATH within a module that has a > dependency on another module that edits path; if you do, you get a duplicate > declaration error. Really we should have a type & provider for managing the system path. I've filed this as https://projects.puppetlabs.com/issues/16048 Josh [1] http://projects.puppetlabs.com/issues/11276 -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
