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

xDnsServerSetting: 'DsAvailable' Key not in Test- and Set-TargetResource in Version 1.9.0.0 #66

Closed
pedrr opened this issue Mar 29, 2018 · 4 comments
Labels
bug The issue is a bug.

Comments

@pedrr
Copy link

pedrr commented Mar 29, 2018

The Property 'DsAvailable' is returend by Get-TargetResource but cannot be tested.

Error Message: The PowerShell DSC resource returned results that are not valid from Get-TargetResource. The DsAvailable key is not a valid property in the corresponding DSC resource schema file. The results from Get-TargetResource must be in a Hashtable format. The keys in the Hashtable must be the same as the properties in the corresponding DSC resource schema file.
Message ID: GetOperationResultInvalidResultFormat

i think this property is missing in the Test and Set Statement.

@johlju
Copy link
Member

johlju commented Mar 29, 2018

If this property DsAvailable can be set to a value, then it is missing in the schema.mof, and in the Set- and Test-TargetResource function. If DsAvailable is a read only value, then schema.mof should be updated to add this property with the Read qualifier to make it a read-only property.

@claudiospizzi
Copy link
Contributor

image

The property is readonly. I will create a PR with a new Read property.

@johlju johlju added bug The issue is a bug. in progress The issue is being actively worked on by someone. labels Apr 27, 2018
johlju pushed a commit that referenced this issue Apr 27, 2018
@SteveL-MSFT SteveL-MSFT added this to In progress in powershell/dscresources May 14, 2019
@SteveL-MSFT SteveL-MSFT removed this from In progress in powershell/dscresources Nov 27, 2019
@rchristman89
Copy link

@johlju Should this issue be closed?

@johlju
Copy link
Member

johlju commented Apr 12, 2020

Yes looks like this was fixed in PR #69.

@johlju johlju closed this as completed Apr 12, 2020
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Feb 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug.
Projects
None yet
Development

No branches or pull requests

4 participants