What's Changed
Bug Fixes
- feat(database): add support for point-in-time restore with creation_s… by @abhishekaryams in #141
Other Changes
- feat(metadata): add approved module metadata by @jaredfholgate in #212
- fix: honor SQL private endpoint settings by @jaredfholgate in #217
- docs: explain SQL Server telemetry upgrade requirements by @jaredfholgate in #229
- fix(database): preserve restore and recovery inputs by @jaredfholgate in #230
Full Changelog: v0.2.1...v0.3.0
Upgrade and compatibility notes
This release includes the merged restore regression fix from #230: Recovery and Restore once again accept recover_database_id and restore_dropped_database_id without requiring creation_source_database_id, preserving v0.2.1 mode compatibility. Other create-mode checks remain unchanged.
Telemetry remains enabled by default and now uses subscription-scope Microsoft.Resources/deployments through AzAPI. While telemetry is enabled, ensure subscription permissions for Microsoft.Resources/deployments/read, write, and delete, or set enable_telemetry = false intentionally. Keep legacy providers available for one final initialization/apply that processes telemetry-only removed blocks (destroy = false) from existing state.
The module now requires AzAPI ~> 2.12 (from ~> 2.4), and examples use Azure/avm-utl-naming/azure 0.2.0. Existing private endpoint resource addresses stay in place, but endpoint lock/role-assignment options are now effective; review first-upgrade plans for newly managed endpoint locks/assignments.
Qualification and limits
Qualified on the merged restore-fix candidate before merge at ffbf8004e6612fa9d737cdd9a964c8709aabcbd5 (tree 1542555eee301c89b92518d1890624a853a084c9) with official Avm.Authoring 1.1.1/Terraform 1.17.2: 29/29 unit runs, 14 native closures/42 commands, and local+hosted 10-step gates including policy passed; CodeQL and CLA passed. Integration suites are absent (0 runs), E2E/examples-test remained held, and real Azure recovery/restore or live-state migration was not performed.