v15.0.1-preview0010
Pre-release
Pre-release
dscbot
released this
09 Jan 16:06
·
190 commits
to main
since this release
[v15.0.1-preview0010]
Changed
- SqlServerDsc
- Renamed
master
branch tomain
(issue #1660). - The module manifest property
DscResourcesToExport
now updates automatically
using the pipeline. - Removed
Export-ModuleMember
from DSC resource that still had it. - The variable
$env:COMPUTERNAME
does not exist cross-platform which
hinders development and testing on macOS and Linux. Instead the
resources have been update to use the helper functionGet-ComputerName
which returns the current computer name cross-plattform.
- Renamed
Fixed
- SqlAGDatabase
- Fix for issue (issue #1492)
added AutomaticSeeding for this resource. In Set-TargetResource added logic that looks
at all replicas of an availability group. When automatic seeding is found, it will use that. - Lots of extra tests to check AutomaticSeeding.
- The parameter
BackupPath
is still needed just in case a database never has been backuped before. - Fixed a typo.
- Fix for issue (issue #1492)
- SqlMaxDop
- Fixes (issue #396).
Added three return values in Get-Target resource.
- Fixes (issue #396).
- SqlProtocol
- Changed KeepAlive Type from UInt16 to Int32 to reflect the actual WMI.ManagementObject
Fixes #1645 (issue #1645). - The verbose messages now correctly show that
$env:COMPUTERNAME
is used
to get or set the configuration, while parameter ServerName is used
to restart the instance.
- Changed KeepAlive Type from UInt16 to Int32 to reflect the actual WMI.ManagementObject
- SqlProtocolTcpIp
- The verbose messages now correctly show that
$env:COMPUTERNAME
is used
to get or set the configuration, while parameter ServerName is used
to restart the instance.
- The verbose messages now correctly show that
- SqlDatabaseMail
- Now if a non-mandatory property is not part of the configuration it will
not be enforced (issue #1661).
- Now if a non-mandatory property is not part of the configuration it will
- SqlSetup
- When the SqlSetup detects that the expected components was not installed
and consequently throws an exception, that exception message now presents
a link to an article on how to find the SQL Server setup logs (issue #1420).
- When the SqlSetup detects that the expected components was not installed
- SqlRSSetup
- If parameter
EditionUpgrade
is set to$false
the/EditionUpgrade
argument is no longer wrongly added (issue #1398).
- If parameter
- SqlServerDsc.Common
- Updated
Get-ServerProtocolObject
, helper function to ensure an exception is
thrown if the specified instance cannot be obtained (issue #1628).
- Updated