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
(MODULES-6904) Restart SQL Server Service with Dependent Services #315
(MODULES-6904) Restart SQL Server Service with Dependent Services #315
Conversation
metadata.json
Outdated
}, | ||
{ | ||
"name": "puppetlabs/powershell", | ||
"version_requirement": ">= 1.0.0" |
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.
Worth noting that I did in fact test this on many versions of the powershell module starting with 1.0.1 which is the earliest version available on the forge.
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.
Just changed the version to >= 1.0.1
since that's the earliest on the forge.
753fb0e
to
8a66b99
Compare
looks grand, bar the check failing and the changelog. |
a16e5f3
to
211ffdf
Compare
Prviously, the sp_configure.pp file would attempt to use the builtin service resource to restart the MSSQLServer service if a configuration change was made. This attempt would fail if there was a dependent service such as the SQL Agent service, which is extremely common. This change implements an extremely small PowerShell script instead to force restart the MSSQLSERVER service, even if there are dependent services. In testing this resulted in the Agent service going down and then coming back up as expected.
211ffdf
to
35bb1a7
Compare
@tphoney Both the failing tests and the changelog issues have been addressed. See the ticket comments also for the passing adhoc run. |
Prviously, the sp_configure.pp file would attempt to use the builtin
service resource to restart the MSSQLServer service if a configuration
change was made. This attempt would fail if there was a dependent
service such as the SQL Agent service, which is extremely common.
This change implements an extremely small PowerShell script instead to
force restart the MSSQLSERVER service, even if there are dependent
services.
In testing this resulted in the Agent service going down and then
coming back up as expected.