-
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
xSQLServerRSConfig: Remove parameter SQLAdminCredential #568
Comments
Ok, I've made the changes to make $SQLAdminCredential optional, but I have two problems:
|
To have a flow I think we could go with 1.3, what do you think? After the first PR is merged, you can rebase the second PR (always rebase, no pull or merge) which will get the commit history in the right order and then replay each commit onto of that (after any conflicts are resolved). |
Yeah, I agree with 1.3, review in order, rebase before the next PR. |
I'll create a PR for this issue, since I'd like to discuss $SQLAdminCredential in the code... |
xSQLServer module aims to drop WMF 4.0 support. WMF 5.0 and later supports a common parameter (PsDscRunAsCredential) for running DSC resources under different credentials, which eliminates the need for the $SQLAdminCredential parameter.
xSQLServer module aims to drop WMF 4.0 support. WMF 5.0 and later supports a common parameter (PsDscRunAsCredential) for running DSC resources under different credentials, which eliminates the need for the $SQLAdminCredential parameter.
I change the title of this issue. Since it was discussed in PR #573 that we should remove the parameter SQLAdminCredential |
xSQLServer module aims to drop WMF 4.0 support. WMF 5.0 and later supports a common parameter (PsDscRunAsCredential) for running DSC resources under different credentials, which eliminates the need for the $SQLAdminCredential parameter.
xSQLServer module aims to drop WMF 4.0 support. WMF 5.0 and later supports a common parameter (PsDscRunAsCredential) for running DSC resources under different credentials, which eliminates the need for the $SQLAdminCredential parameter.
xSQLServer module aims to drop WMF 4.0 support. WMF 5.0 and later supports a common parameter (PsDscRunAsCredential) for running DSC resources under different credentials, which eliminates the need for the $SQLAdminCredential parameter.
…eter (#573) - Changes to xSQLServerRSConfig - BREAKING CHANGE: Removed `$SQLAdminCredential` parameter. Use common parameter PsDscRunAsCredential (WMF 5.0+) to run the resource under different credentials. - PsDscRunAsCredential Windows account must be a sysadmin on SQL Server (issue #568). In addition, the resource no longer uses Invoke-Command cmdlet that was used to impersonate the Windows user specified by $SQLAdminCredential. The call also needed CredSSP authentication to be enabled and configured on the target node, which complicated deployments in non-domain scenarios. Using PsDscRunAsCredential solves this problems for us.
This issue was resolved in merged PR #573. Closing this issue. |
There is no need for the $SQLAdminCredential parameter to be mandatory. Remove the restriction.
Update: In pr #573 it was decided to remove SQLAdminCredential. PR title changed accordingly,
The text was updated successfully, but these errors were encountered: