Skip to content
Azure Data Lab Toolkit

Version History

Unreleased

Section titled “Unreleased”

Added

Section titled “Added”
  • Initial Azure Data Lab Toolkit architecture scaffold.
  • Dependency-ordered feature-request catalog and public roadmap.
  • Astro/Starlight documentation site with dark default and light-mode selector.
  • Slidev pitch deck for the vision, architecture, guardrails, and community invitation.
  • GitHub Pages deployment workflow with a production-build internal-link gate.
  • Status vocabulary that distinguishes Current, Committed design, Backlog, Exploratory, Deferred, and Available behavior.
  • Security, licensing, cost, assessment, Fabric, catalogs, testing, and CI/CD architecture guidance.
  • Clear extension boundaries for target providers, capability modules, catalog sources, solution packs, deployment engines, and probes.
  • Separate offline -Plan resolution and Azure-aware, non-mutating -WhatIf comparison contracts.
  • Roadmap metadata that separates technical prerequisites from delivery sequencing.
  • Authoritative S0-S22 delivery segments with Contract, Live, and Release gates.
  • First-class epics for the PowerShell engine, probes and evidence, Windows and Linux guest operations, SQL VM solution pack, remote state, PostgreSQL VM and container paths, Git/CI intent, Key Vault decisions, and Bastion decisions.

Changed

Section titled “Changed”
  • Corrected the Azure SQLVM Toolkit description to identify it as an unfinished predecessor and source of lessons.
  • Aligned the assessment direction with Azure Arc and the migration component in SQL Server Management Studio.
  • Clarified that architecture is committed design and roadmap entries are not shipped functionality.
  • Reordered the roadmap so the managed, Azure VM, and containerized PostgreSQL paths, then Bicep, Terraform, and general Git/CI adapters, precede Fabric.
  • Required a secretStoreDecision for every target and solution pack and a Bastion-first administrativeAccessDecision for every Azure VM.
  • Separated repository engineering CI from the user-facing Git and pipeline capability.

Current limitations

Section titled “Current limitations”
  • No installable PowerShell module.
  • No deployable cmdlets.
  • No released providers or deployment engines.
  • No stable YAML schema or public command contract.
  • No implemented -Plan, -WhatIf, deployment, probe, or teardown workflow.
  • No production security baseline.

The first implementation proof point is SQL Server on Azure VM from YAML through -Plan, -WhatIf, cost review, guarded deployment, probes, evidence, and confirmed teardown with cleanup proof.

Released entries will link to the matching Git tag and GitHub release. Published releases and release notes will define Available behavior; repository implementation and tests define Current behavior; accepted architecture defines Committed design; the roadmap records Backlog, Exploratory, and Deferred work.

The repository-level log is maintained in CHANGELOG.md.