PowerShell Module Mass Production: Templating in the Field
summary
A clear module reference architecture maps API, process, solution and data layers while keeping templating in a shared framework; choices include Plaster, Stucco, Sampler, .NET and PSModuleDevelopment as engines; examples show a mini module and a PSF project, build-time zero-dependency options, automated CI/CD that takes about ten minutes to go from empty repo to PR validation and gallery release, and a performance win when modules compile to single file (DBATools drops load from ~30s to ~3s).
AI-written summary · about
chapters (13)
- 0:00PowerShell module templating intro
- 3:03Module solution architecture
- 8:41Templating engines vs modules
- 11:55Choosing templating engine
- 16:27Key module capabilities
- 19:41Dependencies and build time
- 22:31CI/CD for module mass production
- 25:17Testing PowerShell modules
- 29:10Building modules for performance
- 32:00Demo: mini module & PSF templates
- 33:46Sampler module project
- 39:28Custom templates with PSModuleDev
- 44:45Q&A
related talks
01h 45mWriting Award Winning PowerShell Functions and Script Modules
42mCreating PowerShell Projects and more with Plaster
46mThese Are the Modules You’re Looking For: Packaging and Publishing PowerShell..
52mPowerShell Module Design Rules (and When to Bend Them)
22mIt's Raining Modules
45mBullet-proofing Patterns & Practices
46mFrom Script to Tool: Building Robust, Meaningful Tools with PowerShell
43mPowerShell Tooling