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:
With the new Dev version it is still a problem with long paths. We still got two example files exceeding 129 characters for the resource SqlServerEndpointPermission.
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
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:
johlju
added
high priority
The issue or PR should be resolved first. It is of less priority than the label 'Blocking Release'.
in progress
The issue is being actively worked on by someone.
bug
The issue is a bug.
labels
Dec 5, 2017
- Changes to SqlServerEndpointPermission
- Now the examples files have a shorter name so that resources will not fail
to compile in Azure Automation (issue #934).
vors
removed
the
high priority
The issue or PR should be resolved first. It is of less priority than the label 'Blocking Release'.
label
Dec 7, 2017
Details of the scenario you tried and the problem that is occurring:
With the new Dev version it is still a problem with long paths. We still got two example files exceeding 129 characters for the resource SqlServerEndpointPermission.
3-AddConnectPermissionToAlwaysOnPrimaryAndSecondaryReplicaEachWithDifferentSqlServiceAccounts.ps1
4-RemoveConnectPermissionToAlwaysOnPrimaryAndSecondaryReplicaEachWithDifferentSqlServiceAccounts.ps1
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
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: