Open wibblemonkey opened 6 years ago
@vrdmr Hey Varad, would you mind taking a look at this issue?
Hi @wibblemonkey,
Thanks for reporting the issue. We are looking at it now.
Thanks, Varad
Evaluating the issue - will report back with the proposed change and ETA.
Because there is a easy workaround to use the New- cmdlet, we deprioritize this. The community is welcome to help.
Cmdlet(s)
Set-AzureRmAutomationModule
PowerShell Version
5.1.14393.1884
Module Version
4.0.0
OS Version
10.0.14393.1884
Description
The Set-AzureRmAutomationModule cmdlet appears to have no effect when attempting to update a module in a target automation account. The module reports in the portal that it is importing a later version and reports success, however the module remains unchanged. Attempting the same with New-AzureRmAutomationModule successfully updates the module to the new version as expected, as does importing the new version through the upload facility in the portal.
Debug Output
Script/Steps for Reproduction
Create a minimal Powershell module with .psm1 and .psd1 files and create two zip packages with version 0.1.0 & 0.2.0. Upload the packages to a location in Azure Blob Storage and generate a SAS uri for each.
Upload version 0.1.0 of the module to the target automation account using New-AzureRmAutomationModule with the SAS uri for the version 0.1.0 zip package.
The portal shows the module status as "importing", and then "available" when the import is complete.
Attempt to upload version 0.2.0 of the module to the target automation account using Set-AzureRmAutomationModule with the SAS uri for the version 0.2.0 zip package.
The portal shows the module status as "importing newer version"; however when the status changes to "available", the module has not been updated.