Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Munging should account for ":" in registry key path #296

Open
kruegerkyle95 opened this issue Oct 2, 2023 · 0 comments
Open

Munging should account for ":" in registry key path #296

kruegerkyle95 opened this issue Oct 2, 2023 · 0 comments

Comments

@kruegerkyle95
Copy link

Describe the Bug

When declaring two registry_key resources with the same key path, for example when using the ensure_resources function, catalog compilation will fail if one of the key paths contains a colon and the other doesn't. These should be treated as the same key. For example, managing two registry_key resources whose paths are "HKLM:\Fake\Path" and "HKLM\Fake\Path" will result in an error. But an error will not occur when the two paths are identical, or simply have different casing. The presence of the colon in one of the other results in an error, but it shouldn't, just like a difference in casing shouldn't.

Expected Behavior

The two registry keys should be created.

Steps to Reproduce

ensure_resource(registry_key, { 'HKLM:\Fake\Path' => { ensure => 'present' }, 'HKLM\Fake\Path' => { ensure => 'present' }, })

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants