The DSC project blueprint or how to start a DSC project the right way
summary
A concrete DSC blueprint that separates YAML configuration data from code and compiles it into versioned MOF artifacts, delivered through an Azure DevOps release pipeline and a pull server. It uses composite resources, splatting helpers, Chocolatey integration, and fail‑fast pester tests to catch issues like duplicate IPs before deployment. The build is a one‑script build that emits the five pull artifacts and RSOP manifests, supports scale (customers with 55,000 servers), and the demo applies changes successfully.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:20Agenda
- 2:10DSC overview
- 8:25Configuration data demo
- 15:10Configuration data problem
- 17:55Layers
- 23:04The problem
- 25:10The data
- 30:00The compilation
- 33:10The data model
- 35:00Creating the resources
- 37:10DSC Workshop
- 42:40Managing software
- 48:15Failures
- 51:40Improvements
- 54:40Promotion of Trust
- 55:20Promotion of Trusted Changes
- 56:40Artifacts
- 57:50Release Pipeline
- 58:55Dependency Resolution
related talks
48mAn Opinionated DSC Solution, with Tooling
01h 18mDSC vs. "The Others" - A Song of Configuration Management
01h 39mDefine, Develop and Deploy DSC Resources
45mDesired State Configuration (DSC) Version 3
51mDSC v3: Evolving Declarative Configuration for Modern Systems
44mApplication Provisioning with DSC and Octopus Deploy
03h 28mEntra ID & M365 as Code with DSC
01h 18mBuilding DSC v3 Resources