-
Notifications
You must be signed in to change notification settings - Fork 224
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
SqlPermission: Integration test is missing for this resource #752
Labels
enhancement
The issue is an enhancement request.
Comments
johlju
added
enhancement
The issue is an enhancement request.
help wanted
The issue is up for grabs for anyone in the community.
labels
Aug 13, 2017
johlju
changed the title
xSQLServerPermission: Integration test is missing for this resource
SqlServerPermission: Integration test is missing for this resource
Dec 24, 2017
johlju
changed the title
SqlServerPermission: Integration test is missing for this resource
SqlPermission: Integration test is missing for this resource
Jul 10, 2020
9 tasks
johlju
added a commit
that referenced
this issue
Jul 31, 2022
…urce) (#1778) - SqlServerDsc - The following classes were added to the module: - `ServerPermission` - complex type for the DSC resource SqlPermission. - The following public functions were added to the module (see comment-based help for more information): - `Test-SqlDscIsLogin` - `ConvertFrom-SqlDscServerPermission` - `ConvertTo-SqlDscServerPermission` - `Get-SqlDscServerPermission` - `Set-SqlDscServerPermission` - SMO stubs (used in the unit tests) - Was updated to remove a bug related to the type `ServerPermissionInfo` when used with the type `ServerPermissionSet`. The stubs suggested that the property `PermissionType` (of type `ServerPermissionSet`) in `ServerPermissionInfo` should have been a array `ServerPermissionSet[]`. This conflicted with real SMO as it does not pass an array, but instead a single `ServerPermissionSet`. The stubs was modified to mimic the real SMO. At the same time some old mock code in the SMO stubs was removed as it was no longer in use. - SqlPermission - BREAKING CHANGE: The resource has been refactored. The parameters `Permissions` has been replaced by parameters `Permission`, `PermissionToInclude`, and `PermissionToExclude`. These permissions parameters are now an instance of the type `ServerPermission`. The type `ServerPermission` contains two properties; `State` and `Permission`. This closes the issue [issue #1761](#1761), it also fixes the issues [issue #1773](#1773), [issue #1704](#1704), and [issue #752](#752). - The resource was refactored into a class-based resource. - SqlDatabasePermission - Fixed comment-based help and cleaned up comments. - Fix localized string that referenced 'user' instead of 'principal', and correct localized string ID for each string. - `Set-SqlDscDatabasePermission` - Minor code cleanup.
johlju
removed
the
help wanted
The issue is up for grabs for anyone in the community.
label
Aug 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details of the scenario you tried and the problem that is occurring:
We should add an integration test for this resource.
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: