A vendors perspective
summary
Experience building a PowerShell SDK that moves from two engineers spending one to two weeks per quarter to one engineer spending half a day on updates, using Ginga and Swagger for code generation and shipping a binary SDK2; automated release notes from Jira, CI with Jenkins and Pester, and logging via LogForet; lessons: dynamic help hosted in an AWS bucket was deleted, 50 different PowerCLI installs broke discovery, whatif/Confirm customization caused a dangerous execution bug, and PowerShell 5.1 in-box forces conservative module requirements.
AI-written summary · about
chapters (25)
- 0:00PowerShell module dev intro
- 1:10Speaker background
- 3:37PowerShell history impact
- 6:50What is a module
- 9:21Binary modules efficiency
- 10:22Module visibility troubleshooting
- 13:12Customer feedback on help
- 15:21Supporting multiple versions
- 17:30API versioning compatibility
- 19:39Cross-platform PowerShell 7
- 23:11Module dependencies conflicts
- 27:09Testing QA strategies
- 27:50PowerShell versions framework
- 30:00Upgrading to PS7 limits
- 32:28Automating release notes
- 34:17Publishing modules platforms
- 37:30Pre-release versions updates
- 41:01QA testing Pester Jenkins
- 42:26Acting on test failures
- 43:30Parameter handling defaults
- 45:17Optimizing API calls
- 47:03Logging troubleshooting
- 48:49Logging for development
- 50:12Handling edge cases
- 50:54Documentation sample scripts
related talks
43mPowerShell Tooling
45myear of improvements to your PowerShell editing experience
03h 41mA Scripters Next Step...
28mEmpowering Teams: Transforming Your...
01h 37mMore Game Breaking PowerShell
45mGitHub Actions for Fun and Profit
01h 26mGetting Ahead By Deleting Code
43mState of the Shell (PowerShell 7.6)