Think Abstract, abstracting your PowerShell code
summary
Shows concrete abstractions: a generated API wrapper that turns an OpenAPI/One API schema into PowerShell functions so callers use invoke-restmethod style calls without hand‑parsing JSON, a compatibility shim that handles Windows PowerShell vs 6+ JSON parsing (convertfrom-json vs system.web.extensions and Newtonsoft), and a registry‑driven Windows 11 module that auto‑generates commandlets from per‑command JSON (generate commandlet). Demos run and expose tradeoffs: upfront work and docs cost, fewer copy‑pastes, easier contributions, and simpler auth/error handling.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:03Abstraction in computing
- 3:10Abstraction in PowerShell
- 7:24Why abstract PowerShell
- 11:40API abstraction examples
- 15:59Basic API calls
- 19:16API authentication challenges
- 21:24Simplifying API interactions
- 25:20API version complexity
- 26:22Automated API cmdlet generation
- 28:14Generating API docs
- 29:39Windows 11 registry tweaks
- 31:47Abstracting Windows config
- 32:07PowerShell splatting
- 33:52Taskbar module
- 37:43Registry cmdlet generation
- 39:16When to abstract code
- 41:50Q&A
related talks
47mLeveraging Web Services with PowerShell
47mCode generation From API Swagger Yaml schema to PowerShell module in 4 easy steps
48mAPIs are for Automata, PowerShell is for People
47mPowerShell + AutoRest + Swagger = Instant Modules
01h 33mA hands-on lab working
01h 45mWriting Award Winning PowerShell Functions and Script Modules
03h 41mA Scripters Next Step...
46mFrom Script to Tool: Building Robust, Meaningful Tools with PowerShell