New-AzureAutomationModule (arm) should fail on non-existing contentLink

[trondhindenes]

When adding an automationmodule and pointing to a contentlink that doesn't exist, an (emtpy) module still gets created.

Expected behavior: non-terminating error.

repro: New-AzureAutomationModule -ContentLink "http://nowhere.com/nope.zip" -Name test

[pcgeek86]

Definitely agree on this feedback. Good catch, Trond.

Cheers,
Trevor Sullivan

[devigned]

@jodoglevy thoughts on this one?

[jodoglevy]

I'll open a bug. One thing we're already doing to help in this area -- in our cmdlet docs we are adding this statement:

When importing a PowerShell module into Azure Automation using the New-AzureAutomationModule or Set-AzureAutomationModule cmdlets, the module import is asynchronous. Even if the cmdlet returns successfully, that does not mean module import has succeeded. To check if import has succeeded, use Get-AzureAutomationModule –Name (make sure to get just this module, not all modules) and check that the ProvisioningState field of the module says succeeded.

Should help with folks thinking module imported succeeded when actually it is async

[cormacpayne]

@vrdmr Hey Varad, would you mind seeing if this is still an issue, and if so, seeing if it fits on your team's radar?

[vrdmr]

@sourabhguha @AnatoliB Can you please take a look at this issue? Thanks