Skip to content

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

@kruegerkyle95

Description

@kruegerkyle95

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' }, })

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions