You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
Changes to SqlServerDsc
Add support for validating the code with the DSC ResourceKit
Script Analyzer rules, both in Visual Studio Code and directly using Invoke-ScriptAnalyzer.
Opt-in for common test "Common Tests - Validate Markdown Links".
Updated broken links in \README.md and in \Examples\README.md
Opt-in for common test 'Common Tests - Relative Path Length'.
Updated the Installation section in the README.md.
To speed up testing in AppVeyor, unit tests are now run in two containers.
Adding the PowerShell script Assert-TestEnvironment.ps1 which
must be run prior to running any unit tests locally with Invoke-Pester.
Read more in the specific contributing guidelines, under the section Unit Tests.
Changes to SqlServerDscHelper
Fix style guideline lint errors.
Changes to Connect-SQL
Adding verbose message in Connect-SQL so it
now shows the username that is connecting.
Changes to Import-SQLPS
Fixed so that when importing SQLPS it imports
using the path (and not the .psd1 file).
Fixed so that the verbose message correctly
shows the name, version and path when importing
the module SQLPS (it did show correctly for the
SqlServer module).
Changes to SqlAg, SqlAGDatabase, and SqlAGReplica examples
Included configuration for SqlAlwaysOnService to enable
HADR on each node to avoid confusion
(issue #1182).
Changes to SqlServerDatabaseMail
Minor update to Ensure parameter description in the README.md.
Fixed formatting issues for the function to work with modules other
than SqlServer.
New DSC resource SqlServerSecureConnection
New resource to configure a SQL Server instance for encrypted SQL
connections.
Changes to SqlAlwaysOnService
Updated integration tests to use NetworkingDsc
(issue #1129).
Changes to SqlServiceAccount
Fix unit tests that didn't mock some of the calls. It no longer fail
when a SQL Server installation is not present on the node running the
unit test (issue #983).