-
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
SqlServerLogin: Set default database #1474
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
Mar 13, 2020
Sounds like a new property in the existing resource, so can't see any problems or caveats, at least not now. 🙂 |
bozho
added a commit
to bozho/SqlServerDsc
that referenced
this issue
Mar 26, 2020
bozho
added a commit
to bozho/SqlServerDsc
that referenced
this issue
Mar 27, 2020
bozho
added a commit
to bozho/SqlServerDsc
that referenced
this issue
Mar 27, 2020
bozho
added a commit
to bozho/SqlServerDsc
that referenced
this issue
Mar 31, 2020
bozho
added a commit
to bozho/SqlServerDsc
that referenced
this issue
Apr 8, 2020
bozho
added a commit
to bozho/SqlServerDsc
that referenced
this issue
Apr 10, 2020
johlju
pushed a commit
that referenced
this issue
Apr 11, 2020
- SqlServerLogin - Added `DefaultDatabase` parameter (issue #1474]).
johlju
removed
the
help wanted
The issue is up for grabs for anyone in the community.
label
Apr 25, 2020
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
SqlServerLogin
resource currently does not support setting the default database for logins.Verbose logs showing the problem
N/A
Suggested solution to the issue
Add an optional
DefaultDatabase
parameter.The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
SQL Server edition and version the target node is running
N/A
SQL Server PowerShell modules present on the target node
N/A
The operating system the target node is running
N/A
Version and build of PowerShell the target node is running
Version of the DSC module that was used
I'm happy to provide a patch for this, just wanted to check if there are any caveats/problems I should be aware of...
The text was updated successfully, but these errors were encountered: