Some modules, such as Az (Azure PowerShell), are "metadata-only" modules, that is, they only contain dependencies on other, more granular modules (but the entire tree of modules is released at once, as a single unit). Such modules are not returned by Get-Module -ListAvailable, which is what the PSModule resource uses internally.
As a consequence, this configuration
PSModule Az
{
Name = 'Az'
Ensure = 'Present'
MinimumVersion = '5.5.0'
Repository = 'PSGallery'
}
will install the module correctly, but will never reach a stable state - Test-TargetResource will always return false.
(The resource will also attempt to install the module even if a higher version is already installed.)
A more appropriate way would possibly be to detect the presence of modules using Get-InstalledModule, which is how it was done in the PowerShellGet 2.x PackageManagement provider interface (Get-InstalledPackage, Get-InstalledModuleDetails).
Some modules, such as
Az(Azure PowerShell), are "metadata-only" modules, that is, they only contain dependencies on other, more granular modules (but the entire tree of modules is released at once, as a single unit). Such modules are not returned byGet-Module -ListAvailable, which is what thePSModuleresource uses internally.As a consequence, this configuration
will install the module correctly, but will never reach a stable state -
Test-TargetResourcewill always returnfalse.(The resource will also attempt to install the module even if a higher version is already installed.)
A more appropriate way would possibly be to detect the presence of modules using
Get-InstalledModule, which is how it was done in the PowerShellGet 2.x PackageManagement provider interface (Get-InstalledPackage, Get-InstalledModuleDetails).