-
Notifications
You must be signed in to change notification settings - Fork 225
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
Issue in setting multiple DB roles for one SQL login with MSFT_xSQLServerDatabaseRole #108
Comments
You are correct. This seems to be a bug. Right now it only supports unique logins regardless of database. |
This should be able to handle different instances on the same server as well |
And maybe make 'Role' as an array to grant multiple roles for one login? |
That too. That would be a nice enhancement as well. |
This resolves issue dsccommunity#99 and issue dsccommunity#108.
@sunbinzhu and @typozh I have fixed this issue, but before I can PR I need to write a test for this resource. I will PR this weekend. But if you want to try it out you can find the fixed resource in my working branch in my fork of xSQLServer |
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
@kwirkykat Can you add breaking change tag to this issue? |
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue dsccommunity#99 and issue dsccommunity#108.
This resolves issue #99 and issue #108. Added $script scope to currentPath variable Fixed style to align with the style guide Set-method did not throw on error Added test for the resource xSQLServerDatabaseRole Changes to en-US strings. Resolved that backspace was not escaped. Now it shows a backspace between server and instance in messages.
This issue was resolved in merged PR #115. Let us know if there is any further problems. |
I met error when I use MSFT_xSQLServerDatabaseRole to grant db_owner role to one SQL login for multiple databases. For example, i want to grant UserA the db_owner role for DB1, DB2, DB3, i created 3 configuration items, with 'Name' as UserA, and 'Database' as DB1, DB2, DB3 separately. It failed to deploy because 'Name' is the only Key parameter for MSFT_xSQLServerDatabaseRole. And i had specified 3 items with same key but different values. Promoting parameter 'Database' as the second Key can fix this error.
My question is whether what i am doing is the correct way to grant multiple DB roles for one SQL login? If so I think you shall promote Database as Key as well. If not, please advise what is the correct way. Thanks.
The text was updated successfully, but these errors were encountered: