Desired State Configuration v3
summary
DSCv3 claims a cloud‑native, cross‑platform configuration engine that actually uses JSON/YAML/Bicep and command‑line adapters so resources can be Python C# or PowerShell; it removes the old no Local Configuration Manager model and adds assertions and an export supported if resource implements it operation. Demos show Bicep compiling to ARM/JSON and applying to DevBox, a registry resource and PowerShell/WMI adapters working, JSON machine‑readable output, and that parallelism and some exporters are intentionally deferred.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:04DSC v1 vs v2 vs v3
- 12:23DSC v3 new features
- 20:28PowerShell resource adapters demo
- 22:56Assertions in configs demo
- 25:47WMI adapter demo
- 27:33Bicep integration demo
- 36:41DevBox integration
- 43:03Q&A
related talks
45mDesired State Configuration (DSC) Version 3
51mDSC v3: Evolving Declarative Configuration for Modern Systems
01h 18mBuilding DSC v3 Resources
01h 52mThe DSC project blueprint or how to start a DSC project the right way
46mManaging Server State using Configuration as Code
41mManaging Advanced DSC Configurations and Configuration Data
01h 18mDSC vs. "The Others" - A Song of Configuration Management
45mWriting DSC Resources for Azure Policy Guest Configuration - For...