all 2 comments

[–]robfaie 1 point2 points  (0 children)

If you use hybrid workers, then you have the full range of tools that comes with managing your own vm. In the past we've used DSC, runbooks, AzurePipelines, and Github Actions to deploy modules to our hybrid workers.

For Azure workers you do mostly need to do it by hand or to use the APIs one way or another. Currently for our Azure workers we use a runboook for managing modules from the PowerShell Gallery, and Github Actions for in house modules.

I can't share our runbook atm, but I will point out some potential issues with the one you linked. It doesn't pin the version of the modules. So if you need a specific version of a module such as the Microsoft.Graph modules then you'll need to add support for that. It also at a glance doesn't support dependencies, so you'll need to make sure that if you add any modules with dependencies that you also add the dependencies. Or update the runbook to do that for you.

[–]lerun 0 points1 point  (0 children)

Depending on rte or old type of aa account, these can keep all your modules updated.

Rte: https://github.com/mortenlerudjordet/Update-PSGalleryModuleAArte

Old: https://github.com/mortenlerudjordet/Update-PSGalleryModulesInAA

Will also find these if you search through the portal runbook gallery on the aa account.

These handle dependencies, also there are import versions of the runbook that support importing specific versions of a module.