Skip to main content

The command was found in the module PowerShellGet, but the module could not be loaded.

While testing a PowerShell DSC script deployed by Azure Automation on an Azure Virtual Machine I ran against the following error message: 

The command <command> was found in the module PowerShellGet, but the module could not be loaded.

What I tried to accomplish was automatically installing the PowerShell Az modules with the following PowerShell DSC script.

# Import DSC modules
Import-DscResource -ModuleName "PowerShellGet" -ModuleVersion 2.2.5

Node $AllNodes.NodeName
{
  PSModule "Az" {
    Ensure             = "Present"
    Name               = "Az"
    Repository         = "PSGallery"
    InstallationPolicy = "Trusted"
    AllowClobber       = $true
    Force              = $true
    RequiredVersion    = 5.6.0
  }
}

To solve this issue you also have to import the PackageManagement module because PowerShellGet has a dependency on this module. The correct version of the script is thus:

# Import DSC modules
Import-DscResource -ModuleName "PackageManagement" -ModuleVersion 1.4.4
Import-DscResource -ModuleName "PowerShellGet" -ModuleVersion 2.2.5

Node $AllNodes.NodeName
{
  PSModule "Az" {
    Ensure             = "Present"
    Name               = "Az"
    Repository         = "PSGallery"
    InstallationPolicy = "Trusted"
    AllowClobber       = $true
    Force              = $true
    RequiredVersion    = 5.6.0
  }
}

Update (March, 15th)

The PowerShellGet module has a specific dependency on version 1.4.4 of the PackageManagement module. You can see it defined in the manifest file (PowerShellGet.psd1).

RequiredModules   = @(@{ModuleName = 'PackageManagement'; ModuleVersion = '1.4.4' })
Labels:

Comments

Post a Comment

Popular posts from this blog

Permantly delete an AD object

At the moment I am busy with PowerShell DSC scripts that also create objects within the Active Directory. Because it's work in progress you have to delete those objects regularly. Witin this sandbox environment the recycle bin feature is enabled so the objects are kept 30 days.  To permantly delete such objects (so you have a clean testing situation) you can use the following PowerShell command. Get-ADObject -filter {sAMAccountName -eq "<name of object>$"} -includeDeletedObjects -property * | Remove-ADObject
Post a Comment
Read more

Make steps conditional in multi-stage YAML pipelines

To make the switch from the graphical release pipelines in Azure DevOps I am missing two features. The first one is to be able to defer a deploy and the second one is to exclude certain deployment steps without the need for editing the YAML file.  The defer option is something Microsoft has to solve in their Azure DevOps proposition. It's a feature which you have in the graphical release pipeline but what they have not implemented yet in their YAML pipeline replacement. Approvals and certain gate conditions are implemented on the environment but the defer option is still missing .  Pipeline The conditional deployment option can be implemented with the help of runtime parameters and expressions . In the parameter section you define boolean parameters which will control the deploy behavior. With the expressions you can control which stage/job/task should be executed when the pipeline runs. In the below YAML sample I experimented with conditions in the azure-pipelines.yml ...
Post a Comment
Read more

Solving Azure DevOps Workload Identity Federation service connection 50 minute time-out error

 When connecting to external resources like Azure Resource Manager you will need a service connection in Azure DevOps. Normally I utilize a service principal for this purpose. The certificate issued by Microsoft Entra ID was normally valid for two years but Microsoft changed this to three months in the release of January 18th and is promoting the usage of Workload identity federation  (WIF). When testing this WIF based service connection I noticed that the OIDC token is only valid for about 50 minutes. This time is to short for the PowerShell script I use to monitor the Azure Image Builder image builds. These image build processes can take up to four hours but fail now with an error message like the one below. A configuration issue is preventing authentication - check the error message from the server for details. You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details.  Original exception: AADSTS700...
Post a Comment
Read more