-
Notifications
You must be signed in to change notification settings - Fork 225
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
xSQLServerAlwaysOnAvailabilityGroupReplica: Hash table returned from get-method does not match schema #477
Comments
@johlju, I'm going to take this and work on it. |
Thanks for detailing the issue @johlju. I'm going to try and document why some of the supplied parameters are not included in the hashtable that is returned from Get-TargetResource.
|
@randomnote1 depending on issue PowerShell/DscResources#318 we should either add these properties to the hash table or leave it as is (except for the missing read properties that should be added). Setting this as in progress for the time being. |
I'm ready to submit the PR for this. Just waiting on the decision! |
Please submit the PR. It's an approvement. I meant that we can start to enforce the rule once the issue in DscResources are "approved"/correct. :) |
Gotcha. PR submitted. |
Details of the scenario you try and problem that is occurring:
The hash table that is returned from the Get-method does not contain the following properties
PrimaryReplicaSQLServer
PrimaryReplicaSQLInstanceName
EndpointHostName
Regarding
EndpointHostName
, the hash table return the read only propertySQLServerNetName
, are that actually suppose to be set toEndpointHostName
instead?The hash table do contain this property which is not part of the schema. These should be added as read only properties.
EndpointUrl
EndpointPort
The DSC configuration that is using the resource (as detailed as possible):
n/a
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev
The text was updated successfully, but these errors were encountered: