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:
This block is the problem in the below code. Before this block $testParameters contains 4 keys (InstanceName, etc). Instead of adding two more keys, this block of code changes the $testParameters to only contain these two keys (Ensure, Permission). But why it do work in the debugger and not in the PowerShell prompt is a mystery. 😄
- Changes to xSQLServerEndpointPermission
- Fixed a problem when running the tests locally in a PowerShell console it
would ask for parameters (issue dsccommunity#897).
- Changes to xSQLServerAvailabilityGroupListener
- Fixed a problem when running the tests locally in a PowerShell console it
would ask for parameters (issue dsccommunity#897).
- Changes to xSQLServerEndpointPermission
- Fixed a problem when running the tests locally in a PowerShell console it
would ask for parameters (issue dsccommunity#897).
- Changes to xSQLServerAvailabilityGroupListener
- Fixed a problem when running the tests locally in a PowerShell console it
would ask for parameters (issue dsccommunity#897).
- Changes to xSQLServerEndpointPermission
- Fixed a problem when running the tests locally in a PowerShell console it
would ask for parameters (issue #897).
- Changes to xSQLServerAvailabilityGroupListener
- Fixed a problem when running the tests locally in a PowerShell console it
would ask for parameters (issue #897).
Details of the scenario you tried and the problem that is occurring:
This block is the problem in the below code. Before this block
$testParameters
contains 4 keys (InstanceName, etc). Instead of adding two more keys, this block of code changes the$testParameters
to only contain these two keys (Ensure, Permission). But why it do work in the debugger and not in the PowerShell prompt is a mystery. 😄Changing the block to this resolves the problem.
https://github.com/PowerShell/xSQLServer/blob/61862e73f3bc4067e1217f42e04d761bf96a19b7/Tests/Unit/MSFT_xSQLServerEndpointPermission.Tests.ps1#L171-L205
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:
Windows 10.
PS > $PSVersionTable
Name Value
PSVersion 5.1.17025.1000
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17025.1000
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
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: