Skip to content
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

Closed
bozho opened this issue May 23, 2017 · 6 comments
Closed

xSQLServerRSConfig: Remove parameter SQLAdminCredential #568

bozho opened this issue May 23, 2017 · 6 comments
Labels
enhancement The issue is an enhancement request.

Comments

@bozho
Copy link
Contributor

bozho commented May 23, 2017

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,

bozho added a commit to bozho/SqlServerDsc that referenced this issue May 23, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 23, 2017
@bozho
Copy link
Contributor Author

bozho commented May 24, 2017

Ok, I've made the changes to make $SQLAdminCredential optional, but I have two problems:

  1. I'd like to fix issues xSQLServerRSConfig: Replace sqlcmd.exe with Invoke-Sqlcmd calls #567, xSQLServerRSConfig: Remove parameter SQLAdminCredential #568, xSQLServerRSConfig: Virtual directory creation for SQL 2016 #569 and xSQLServerRSConfig: Configurable URL reservations #570 in order (xSQLServerRSConfig: Remove parameter SQLAdminCredential #568 branch off xSQLServerRSConfig: Replace sqlcmd.exe with Invoke-Sqlcmd calls #567, xSQLServerRSConfig: Virtual directory creation for SQL 2016 #569 branch off xSQLServerRSConfig: Remove parameter SQLAdminCredential #568 and so on). If I submit a PR for xSQLServerRSConfig: Remove parameter SQLAdminCredential #568, it is compared to the dev branch in this repository and shows changes from both xSQLServerRSConfig: Replace sqlcmd.exe with Invoke-Sqlcmd calls #567 and xSQLServerRSConfig: Remove parameter SQLAdminCredential #568, which makes it confusing. What would be the best workflow here? Should I wait until xSQLServerRSConfig: Replace sqlcmd.exe with Invoke-Sqlcmd calls #567 is merged and then submit the PR for xSQLServerRSConfig: Remove parameter SQLAdminCredential #568?

  2. We still need to use CredSSP authentication when running Invoke-Sqlcmd with $SQLAdminCredential using Invoke-Command, even though we're running it on the same machine. I don't know how this behaves when run in a domain, but running it on a non-domain machine requires enabling/configuring CredSSP - I'm not sure if we should consider this to be within the remit of this resource, or just document the fact that CredSSP needs to be enabled and configured.

bozho added a commit to bozho/SqlServerDsc that referenced this issue May 24, 2017
@johlju
Copy link
Member

johlju commented May 24, 2017

  1. three ways of doing this I think, either
    1.1 We do and merge each PR in turn before continuing on the next PR.
    1.2 You do all changes (all issues) in one PR.
    1.3 You branch off to a new working branch from the previous working branch (your suggestion above). When sending in a PR for the branched off PR's, write in the PR description which PR(s) it depends on. I will review and merge them in the correct order.

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).

@johlju johlju added enhancement The issue is an enhancement request. in progress The issue is being actively worked on by someone. labels May 24, 2017
@bozho
Copy link
Contributor Author

bozho commented May 24, 2017

Yeah, I agree with 1.3, review in order, rebase before the next PR.

@bozho
Copy link
Contributor Author

bozho commented May 24, 2017

I'll create a PR for this issue, since I'd like to discuss $SQLAdminCredential in the code...

bozho added a commit to bozho/SqlServerDsc that referenced this issue May 24, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 24, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 24, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 25, 2017
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.
johlju pushed a commit to bozho/SqlServerDsc that referenced this issue May 26, 2017
johlju pushed a commit to bozho/SqlServerDsc that referenced this issue May 26, 2017
johlju pushed a commit to bozho/SqlServerDsc that referenced this issue May 26, 2017
johlju pushed a commit to bozho/SqlServerDsc that referenced this issue May 26, 2017
johlju pushed a commit to bozho/SqlServerDsc that referenced this issue May 26, 2017
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.
@johlju johlju changed the title xSQLServerRSConfig: make $SQLAdminCredential an optional argument xSQLServerRSConfig: Remove parameter SQLAdminCredential May 27, 2017
@johlju
Copy link
Member

johlju commented May 27, 2017

I change the title of this issue. Since it was discussed in PR #573 that we should remove the parameter SQLAdminCredential

bozho added a commit to bozho/SqlServerDsc that referenced this issue May 30, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 30, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 30, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 30, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue May 30, 2017
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.
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 1, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 2, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 2, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 2, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 2, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 2, 2017
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.
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 2, 2017
kewalaka added a commit to kewalaka/xSQLServer that referenced this issue Jun 4, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 5, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 5, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 5, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 5, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 5, 2017
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.
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 5, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 5, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 5, 2017
bozho added a commit to bozho/SqlServerDsc that referenced this issue Jun 6, 2017
johlju pushed a commit that referenced this issue Jun 6, 2017
…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.
@johlju
Copy link
Member

johlju commented Jun 8, 2017

This issue was resolved in merged PR #573. Closing this issue.

@johlju johlju closed this as completed Jun 8, 2017
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Jun 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request.
Projects
None yet
Development

No branches or pull requests

2 participants