Home Dashboard Directory Help
Search

Test-TargetResource in MSFT_RegistryResource Missing Force Parameter by Steve Murawski


Status: 

Closed
 as Fixed Help for as Fixed


5
0
Sign in
to vote
Type: Bug
ID: 792354
Opened: 7/2/2013 12:56:50 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

The parameter sets for Test-TargetResource and Set-TargetResource do not match for MSFT_RegistryResource.

For Set-TargetResource you have:
[parameter(Mandatory = $true)]                
        [ValidateNotNullOrEmpty()]
        [System.String]
        $Key,
        
        [ValidateNotNull()]
        [System.String]
        $ValueName = [String]::Empty,
        
        [ValidateSet("Present", "Absent")]
        [System.String]
        $Ensure = "Present",

        [ValidateNotNull()]
        [System.String[]]
        $ValueData = @(),

        [ValidateSet("String", "Binary", "DWord", "QWord", "MultiString", "ExpandString")]
        [System.String]
        $ValueType = "String",
        
        [System.Boolean]
        $Hex = $false,
        
        [System.Boolean]
        $Force = $false

For Test-TargetResource you have:

[parameter(Mandatory = $true)]                
        [ValidateNotNullOrEmpty()]
        [System.String]
        $Key,
        
        [ValidateNotNull()]
        [System.String]
        $ValueName = [String]::Empty,
        
        [ValidateSet("Present", "Absent")]
        [System.String]
        $Ensure = "Present",

        [ValidateNotNull()]
        [System.String[]]
        $ValueData = @(),

        [ValidateSet("String", "Binary", "DWord", "QWord", "MultiString", "ExpandString")]
        [System.String]
        $ValueType = "String",
        
        [System.Boolean]
        $Hex = $false
Details
Sign in to post a comment.
Sign in to post a workaround.