-
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
Invoke-query updated to allow smo object #1380
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #1380 +/- ##
=====================================
+ Coverage 98% 98% +<1%
=====================================
Files 36 36
Lines 5344 5354 +10
=====================================
+ Hits 5238 5248 +10
Misses 106 106 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 3 files at r1, 1 of 1 files at r2.
Reviewable status: all files reviewed, 6 unresolved discussions (waiting on @kungfu71186)
Modules/SqlServerDsc.Common/SqlServerDsc.Common.psm1, line 1617 at r2 (raw file):
SQLServer Server1 -SQLInstanceName MSSQLSERVER
These parameters should not be needed when piping using an *.Server object?
Modules/SqlServerDsc.Common/SqlServerDsc.Common.psm1, line 1668 at r2 (raw file):
# If we don't have an smo object, then we try to use credentials
This comment seem misplaced to me, should it be moved or just removed?
Modules/SqlServerDsc.Common/SqlServerDsc.Common.psm1, line 1671 at r2 (raw file):
$smoConnectObject
Can we leave the previous variable name $serverObject
? It is the actual *.server object that is returned (not a connect object that should be used to get a server object?).
Throughout.
Modules/SqlServerDsc.Common/SqlServerDsc.Common.psm1, line 1675 at r2 (raw file):
Paramaters
Parameters
Typo. 🙂
Throughout.
Tests/Unit/SqlServerDsc.Common.Tests.ps1, line 1532 at r2 (raw file):
Context 'Execute a query with piped SMO server object' {
It is not really using piping in this context block, it using the SqlServerObject parameter.
Tests/Unit/SqlServerDsc.Common.Tests.ps1, line 1553 at r2 (raw file):
Context 'Execute a query with results' {
Here it is using piping so maybe the description in the context block should say that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: all files reviewed, 6 unresolved discussions (waiting on @johlju)
Modules/SqlServerDsc.Common/SqlServerDsc.Common.psm1, line 1617 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
SQLServer Server1 -SQLInstanceName MSSQLSERVER
These parameters should not be needed when piping using an *.Server object?
Done.
Modules/SqlServerDsc.Common/SqlServerDsc.Common.psm1, line 1668 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
# If we don't have an smo object, then we try to use credentials
This comment seem misplaced to me, should it be moved or just removed?
Done.
Modules/SqlServerDsc.Common/SqlServerDsc.Common.psm1, line 1671 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
$smoConnectObject
Can we leave the previous variable name
$serverObject
? It is the actual *.server object that is returned (not a connect object that should be used to get a server object?).Throughout.
Done.
Modules/SqlServerDsc.Common/SqlServerDsc.Common.psm1, line 1675 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Paramaters
Parameters
Typo. 🙂Throughout.
Done.
Tests/Unit/SqlServerDsc.Common.Tests.ps1, line 1532 at r2 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Context 'Execute a query with piped SMO server object' {
It is not really using piping in this context block, it using the SqlServerObject parameter.
oops. context descriptions got flipped.
Tests/Unit/SqlServerDsc.Common.Tests.ps1, line 1553 at r2 (raw file):
oops. context descriptions got flipped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 2 files at r3.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @kungfu71186)
CHANGELOG.md, line 77 at r3 (raw file):
- Changes to common module: Invoke-Query
There was a release yesterday, so could you please rebase, then make sure this change log entry is moved back to the Unreleased section.
@johlju hopefully good now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r4.
Reviewable status: complete! all files reviewed, all discussions resolved
Pull Request (PR) description
This Pull Request (PR) fixes the following issues
Fixes #1355
Closes #1356
Task list
Entry should say what was changed, and how that affects users (if applicable).
and comment-based help.
This change is