-
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
BREAKING CHANGE: Check for SQLPS & SQLServer modules required #91
Comments
If I look at a server with SQL Server 2016 installed without SSMS there is only SQLPS module. So I think if we want to use SQLServer before SQLPS, then the check should be switched. Like below. Or am I missing something?
|
Indeed - I wrote it very quickly last night to make sure that it was recorded as an issue to be aware of Even moreso if the SQLServer Module gets published to the PowerShell Gallery as it wont require SSMS to be installed on that machine as well. |
If it gets published to the gallery (and updated more frequently than SQL Server/SSMS) then it would be nice to have the option in the setup resource to pull that from the galley and install it. |
I think this issue also needs to make sure that tests are run using both SQLPS and SQLServer stub module. If SQLServer module will be the preferred module if it exists. Then all tests needs to be verified to be able to work with both modules. |
We also need to add a control question for this in the GitHub ISSUE_TEMPLATE - if the user is using SQLPS och SQLServer module, and what version om the module. |
Changed helper function Import-SQLPSModule to support SqlServer module (issue dsccommunity#91). The SqlServer module is the preferred module so if it is found it will be used, and if not found an attempt will be done to load SQLPS module instead. Added new control question to ISSUE_TEMPLATE to know which module the user is using when submitting an issue.
- Changes to xSQLServerHelper module - BREAKING CHANGE: Changed helper function Import-SQLPSModule to support SqlServer module (issue #91). The SqlServer module is the preferred module so if it is found it will be used, and if not found an attempt will be done to load SQLPS module instead. - Changes to xSQLServerScript - Updated tests for this resource, because they failed when Import-SQLPSModule was updated. - Changes to ISSUE_TEMPLATE - Added new control question to ISSUE_TEMPLATE to know which module the user is using when submitting an issue.
With the latest updates to SSMS the SQLPS module was renamed to SQLServer so with this in mind we should have a check in all the resources for the change of module name for this along the lines of
Though this would need to be actioned in the same way across all of the resources where
is currently in place
The text was updated successfully, but these errors were encountered: