Thanks John! It appears to open a ticket I do so on the GitHub site by logging in, is this correct?
The reason for suspecting the lack of string termination is due to what we see in the Registry GUI, which is random characters and words after the string, then you hit Refresh on the page, the random characters and strings change. It does seem specific to a hyphen being in the string, but I will test again to be certain. Thanks! Mark On Monday, April 27, 2015 at 9:06:31 AM UTC-5, jcbollinger wrote: > > > > On Friday, April 24, 2015 at 1:52:17 PM UTC-5, Mark Wolek wrote: >> >> We believe this has something to do with puppet inserting strings that >> are not null terminated, but I've had no luck at all adding termination to >> the string... have tried single and double quoting it. \x0 \00 \000 so >> many types of termination tried but nothing seems to do the trick... >> >> > > Having examined the source of the latest version of this module, I can > tell you that Puppet relies on registry support from the Ruby standard > library to handle the low-level details of registry manipulation. As far > as I can tell, Puppet's own code does not do any parsing or processing of > registry values that would be sensitive to a hyphen character in the > string. Were you speculating about that being related to the problem, or > do you in fact see different results when the array elements do not contain > hyphens? > > I am anyway inclined to think that the problem is NOT wrong string > termination, at least of the values you specify in your manifest, because > Get-ItemProperty is giving you an array value in which the first element > appears completely correct. The problem could, however, be related to > incorrectly specifying the size of the *array* to Windows, or failing to > provide an array terminator (I'm not much of a registry tinkerer, so I'm > not sure which would actually be applicable). > > I encourage you to file a ticket against the module. I am uncertain > whether the issue is there or in the Ruby standard library because the docs > of the relevant library class suffer from the vagueness typical of Ruby > docs, but the module maintainers are best positioned to evaluate that. > Even if the problem turns out to be in the underlying Ruby library, it does > not appear that the module's tests include any that exercise setting or > retrieving values of type "array", and a ticket against the module > *should* result at least in addition of such tests. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c0503ad5-5d72-48ed-868f-522491f93e78%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
