Building DSC v3 Resources
summary
DSC v3 requires JSON as its canonical I/O and uses YAML only as a human layer; manifests follow a manifest JSON schema and register by filename. Demo wraps Windows tzutil and succeeds at setting the timezone, then builds a compiled .NET self-contained binary (TS Toys) with a command‑line parser, serializes/deserializes config JSON, publishes a resource manifest, and uses the dsc CLI and VS Code schema completion to register and run get/set. One live bug in stdin handling is found and fixed on the demo; overall resources execute.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:14What is DSC
- 8:06DSC v3 changes
- 13:03Installing DSC v3
- 27:00Designing DSC resources
- 39:48TZUtil as DSC resource
- 51:52Custom binary resource in C#
- 1:08:06Wrapping custom binary
- 1:15:30Key takeaways and closing remarks
related talks
51mDSC v3: Evolving Declarative Configuration for Modern Systems
51mImproving Shell usability -DSCv3
44mDesired State Configuration v3
01h 52mThe DSC project blueprint or how to start a DSC project the right way
01h 39mDefine, Develop and Deploy DSC Resources
01h 18mDSC vs. "The Others" - A Song of Configuration Management
45mSet up your dev machine in record time with WinGet and Desired State Configuration
45mWriting DSC Resources for Azure Policy Guest Configuration - For...