You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring:
When using SqlServiceAccount with the following configuration, I'm expected Get-TargetResource to also return 'DatabaseEngine' and 'SqlServerAgent' as the service type, but it returns 'SqlServer' and 'SqlAgent' respectively.
[-] Should have set the resource and all the parameters should match 670ms
Expected string length 14 but was 9. Strings differ at index 0.
Expected: {DatabaseEngine}
But was: {SqlServer}
-----------^
103: $resourceCurrentState.ServiceType | Should -Be $mockServiceTypeDatabaseEngine
[-] Should have set the resource and all the parameters should match 1.66s
Expected string length 14 but was 8. Strings differ at index 3.
Expected: {SQLServerAgent}
But was: {SqlAgent}
--------------^
153: $resourceCurrentState.ServiceType | Should -Be $mockServiceTypeSqlServerAgent
I suggest we change this so that Get-TargetResource returns 'DatabaseEngine' and 'SqlServerAgent' to be consistent.
The DSC configuration that is using the resource (as detailed as possible):
johlju
changed the title
SqlServiceAccount: Expected Get-TargetResource to return 'DatabaseEngine'
SqlServiceAccount: Expected Get-TargetResource to return 'DatabaseEngine' and 'SqlServerAgent'
Dec 30, 2017
johlju
added
in progress
The issue is being actively worked on by someone.
and removed
help wanted
The issue is up for grabs for anyone in the community.
labels
Feb 7, 2019
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Feb 7, 2019
- Now the correct service type string value is returned by the function
`Get-TargetResource`. Previously one value was passed in as a parameter
(e.g. `DatabaseEngine`), but a different string value as returned
(e.g. `SqlServer`). Now `Get-TargetResource` return the same values
that can be passed as values in the parameter `ServiceType` (issue dsccommunity#981).
- Changes to SqlServerDsc
- Update integration tests to use the new integration test template.
- Changes to SqlServiceAccount
- Now the correct service type string value is returned by the function
`Get-TargetResource`. Previously one value was passed in as a parameter
(e.g. `DatabaseEngine`), but a different string value as returned
(e.g. `SqlServer`). Now `Get-TargetResource` return the same values
that can be passed as values in the parameter `ServiceType` (issue #981).
Details of the scenario you tried and the problem that is occurring:
When using SqlServiceAccount with the following configuration, I'm expected
Get-TargetResource
to also return 'DatabaseEngine' and 'SqlServerAgent' as the service type, but it returns 'SqlServer' and 'SqlAgent' respectively.I suggest we change this so that
Get-TargetResource
returns 'DatabaseEngine' and 'SqlServerAgent' to be consistent.The DSC configuration that is using the resource (as detailed as possible):
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a
What module (SqlServer or SQLPS) and which version of the module 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: