-
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
SqlServerRole: Add support for nested roles #1452
Labels
enhancement
The issue is an enhancement request.
Comments
9 tasks
johlju
added
enhancement
The issue is an enhancement request.
help wanted
The issue is up for grabs for anyone in the community.
labels
Dec 31, 2019
Sounds like a good addition. |
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
Dec 31, 2019
johlju
changed the title
SqlServerRole: Add support for nested roles.
SqlServerRole: Add support for nested roles
Dec 31, 2019
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
SQL Server supports both logins and user-defined server roles being members of a server role. The SqlServerRole resource should be enhanced to add this support. Currently, the resource checks whether all Members, MembersToInclude, or MembersToExclude are valid Logins on the system.
Verbose logs showing the problem
N/A
Suggested solution to the issue
Instead of solely checking for a valid Login, the resource should also validate whether it matches a Role defined in the instance.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
SQL Server edition and version the target node is running
SQL 2012+
SQL Server PowerShell modules present on the target node
SQLPS
SqlServer
SqlServerDsc
The operating system the target node is running
N/A
Version and build of PowerShell the target node is running
N/A
Version of the DSC module that was used ('dev' if using current dev branch)
dev
The text was updated successfully, but these errors were encountered: