I bet you would agree that importing PowerShell modules to Azure Automation Account using GUI is super annoying. Moreover, if such a module has some dependencies, you have to import them one by one beforehand and often in the correct order too. Not t...
Ahoj Ondreji, I noticed the error message when using "-RuntimeVersion 7.1" parameter as you mentioned in the article (personally I do not need v7.1, but reporting in case you would like to have a look at it).
"New-AzAutomationModule : Cannot validate argument on parameter 'RuntimeVersion'. The argument "7.1" does not belong to the set "5.1,7.2" specified by the ValidateSet attribute. Supply an argument that is in the set and then try the command again."
Hello Ondrej, when trying your New-AzureAutomationModule example, I am getting the following error:
New-PSGetItemInfo : Cannot convert value "2.0.0-rc3" to type "System.Version". Error: "Input string was not in a correct format."
Ondrej Sebela
System Administrator that loves PowerShell
Lewis Thorley
Hello Ondrej,
I know only Runtime Version 5.1 & 7.2 are supported values by Get-AzAutomationModule at time of writing.
https://github[.]com/Azure/azure-powershell/issues/27235#issuecomment-2687160833
I raised a feature request for 7.4 and looks like that will be added by 15/05. It would be great if this could be added to your module after general release.
Thanks for your work on creating this function, it works great :).