Publishing and Managing Modules in an Internal Repository
summary
Concrete checklist: set up publish to a file share and a local NuGet feed and confirm publish/install actually writes and reads packages; run Test-ModuleManifest and import the module locally before publishing; require dependencies already live in the repo or mark them as external module dependencies; automate save-module → test → publish in CI/CD and mirror public modules from PSGallery to control versions; watch NuGet version normalization, API keys, and the special-case behavior of the Az module.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:41How Do You Distribute Powershell
- 4:38Ps Repository Commands
- 7:14Publish a Module
- 12:52External Assemblies
- 14:59Default Parameter Values
- 15:22Load an Api Key
- 20:46Import the Modules
- 23:52Host Public Modules Internally
- 26:29Publish the Modules
- 41:15Questions
related talks
49mPublishing and Managing Modules with an Internal Repository
49mStop manually publishing your modules. Automate it in 2 minutes!
50mGet control of you Git: Managing PS module binaries using VSTS CI/CD and...
01h 27mEverything On-Prem: From Git to Gallery with Open Source
45mGitHub Actions for Fun and Profit
03h 04mMastering Making Modules
45mDon’t Stop at the PowerShell Pipeline. Build a CI/CD Pipeline for your PowerShell
47mBuilding and Publishing Reusable PowerShell Tools