-
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
xSQLServerSetup: Getting warnings when running integration test #798
Labels
enhancement
The issue is an enhancement request.
Comments
johlju
added
enhancement
The issue is an enhancement request.
in progress
The issue is being actively worked on by someone.
labels
Sep 11, 2017
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Sep 11, 2017
- Fixed so integration test does not write warnings when SQLPS module is loaded (issue dsccommunity#798).
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Sep 11, 2017
- Fixed so integration test does not write warnings when SQLPS module is loaded (issue dsccommunity#798).
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Sep 11, 2017
- Fixed so integration test does not write warnings when SQLPS module is loaded (issue dsccommunity#798).
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Sep 11, 2017
- Fixed so integration test does not write warnings when SQLPS module is loaded (issue dsccommunity#798).
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Sep 11, 2017
- Fixed so integration test does not write warnings when SQLPS module is loaded (issue dsccommunity#798).
5 tasks
johlju
added a commit
that referenced
this issue
Sep 12, 2017
- Changes to xSQLServer - Updated appveyor.yml so that integration tests run in order and so that the SQLPS module folders are renamed to not disturb the units test, but can be renamed back by the integration tests xSQLServerSetup so that the integration tests can run successfully. (issue #774). - Changes to xSQLServerHelper - Changes to Connect-SQL and Import-SQLPSModule - Now it correctly loads the correct assemblies when SqlServer module is present (issue #649). - Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server. Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path. - Changes to xSQLServerSetup - Fixed so that the integration test renames back the SQLPS module folders if they was renamed by AppVeyor (in the appveyor.yml file). (issue #774). - Fixed so integration test does not write warnings when SQLPS module is loaded (issue #798).
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:
When running the integration test for this resource I'm seeing a lot of warnings. After a quick search it seems to be because the AppVeyor build worker has the Azure SQL cmdlets installed.
https://social.technet.microsoft.com/Forums/ie/en-US/35b0bf59-b554-46f2-86cd-27e3773c6505/importmodule-sqlps-disablenamechecking-is-returning-a-bunch-of-warnings-i-do-not-want-to-see-in?forum=sqlkjmanageability
I will try to solve this one when I send in a PR to fix another issue.
The DSC configuration that is using the resource (as detailed as possible):
n/a
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
SQL Server 2016
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev
The text was updated successfully, but these errors were encountered: