-
Notifications
You must be signed in to change notification settings - Fork 54
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
Test-DscDnsParameterState: Move enhancements to Test-DscParameterState
in module DscResource.Common
#121
Comments
Tagging @raandree on that one... |
I tried to move this over to After 3 hours of debugging I'm no closer to a solution - |
This test fails: I changed this row to Actually if I add these two rows without the parameter $result = Test-DscParameterState -CurrentValues $currentState -DesiredValues $desiredState -TurnOffTypeChecking
$resultReverse = Test-DscParameterState -CurrentValues $desiredState -DesiredValues $currentState -TurnOffTypeChecking |
The problem is $nameServers = [Microsoft.Management.Infrastructure.CimInstance[]] @(
New-CimInstance -ClassName 'MSFT_KeyValuePair' -Namespace 'root/microsoft/Windows/DesiredStateConfiguration' -Property @{
Key = 'B.ROOT-SERVERS.NET.'
Value = '199.9.14.201'
} -ClientOnly
New-CimInstance -ClassName 'MSFT_KeyValuePair' -Namespace 'root/microsoft/Windows/DesiredStateConfiguration' -Property @{
Key = 'M.ROOT-SERVERS.NET.'
Value = '202.12.27.33'
} -ClientOnly
)
Compare-DscParameterState -CurrentValues @{
IsSingleInstance = 'Yes'
NameServer = @()
} -DesiredValues @{
NameServers = $nameServers
IsSingleInstance = 'Yes'
Verbose = $true
} -TurnOffTypeChecking -ReverseCheck |
Submitted a bug in issue dsccommunity/DscResource.Common#65 |
Test-DscParameterState
in module DscResource.Common
The function
Test-DscDnsParameterState
is enhanced with additional parameters compared to the functionTest-DscParameterState
that is available in the module DscResource.Common.These enhancements should be merged into the function in DscResource.Common so we can remove the duplicate code in this module.
This was discovered when converting this module to the new CI pipeline.
The text was updated successfully, but these errors were encountered: