Create cmdlet or parameter set for setting the context for a background job

[blumu]

Cmdlet(s)

PowerShell Version

PSVersion 5.1.15063.608

Module Version

Azure Powershell 5.0.1

OS Version

10.0.15063.608

Description

Debug Output

The Set-AzureRmContext cmdlet throws a .Net exception Collection was modified; enumeration operation may not execute. when running within Start-Job:

Note: Two related bugs
#2290 and #1835 were closed but the advertised solution (using the new -AzureRmContext parameter) is not practical: it's not necessarily possible to add the -AzureRmContext switch to every command in the script block, especially when auxiliary scripts are called.

DEBUG: 10:13:40 PM - GetAzureRMContextCommand begin processing with ParameterSet 'GetSingleContext'.
DEBUG: 10:13:40 PM - using account id '****@****.com'...


Name             : ****
Account          : ****@****.com
SubscriptionName : ****
TenantId         : ****
Environment      : AzureCloud

DEBUG: AzureQoSEvent: CommandName - Get-AzureRmContext; IsSuccess - True; Duration - 00:00:00.0138074; Exception - ;
DEBUG: Finish sending metric.
DEBUG: 10:13:40 PM - GetAzureRMContextCommand end processing.
DEBUG: 10:13:40 PM - GetAzureRMContextCommand end processing.


Collection was modified; enumeration operation may not execute.
    + CategoryInfo          : CloseError: (:) [Set-AzureRmContext], InvalidOperationException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Profile.SetAzureRMContextCommand
    + PSComputerName        : localhost

**** Some Azure PS command ****

Name             : ****
Account          : ****@****.com
SubscriptionName : ****
TenantId         : ****
Environment      : AzureCloud

Your Azure credentials have not been set up or have expired, please run Login-AzureRMAccount to set up your Azure credentials.
    + CategoryInfo          : CloseError: (:) [Get-AzureRmStorageAccount], ArgumentException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Management.Storage.GetAzureStorageAccountCommand
    + PSComputerName        : localhost

********

Script/Steps for Reproduction

$DebugPreference="Continue"
Get-AzureRmContext | out-host
$j = Start-Job -ScriptBlock {
        param($context)
        Set-AzureRmContext -Context $context
        Write-Host "**** Some Azure PS command ****"
        Get-AzureRmContext | out-host
        Get-AzureRmStorageAccount
        Write-Host "********"
    } -ArgumentList $c
$j | Receive-Job -Wait

[markcowl]

@blumu What are you intending to do with this script? Set-AzureRmContext when used with the Context parameter set is meant to alter an existing context, or to create a context with a new name. If you want to select a context, you should use select-azurermcontext, so for example, the following does what I think you want:

$j = Start-Job -ScriptBlock {
        param($context)
        Select-AzureRmContext -InputObject $context
        Write-Host "**** Some Azure PS command ****"
        Get-AzureRmContext | out-host
        Get-AzureRmStorageAccount
        Write-Host "********"
    } -ArgumentList (Get-AzureRmContext)

There should be an error if you don't choose any paramaters wit the -Context parameter set in Set-AzureRmContext (ideally the parameter set would require at least one additional parameter)

[blumu]

This makes sense now :-) I was just using the wrong command. It would be nice indeed to use a parameter set to prevent calling Set-AzureRmContext without further arguments. Or at least improve error handling and get rid of the Collection was modified; enumeration operation may not execute exception which is not very helpful @markcowl

[markcowl]

@blumu agreed. WIll look at updating the parameter set to prevent this.

[ljtill]

Hey!

Receiving a similar scenario with the AzureRM Module 5.0.1 where the Get-AzureRmContext isn't passing into the Job or the Select-AzureRmContext isn't picking up the $Context. Have been testing a whole load of scenario's this evening and since installing the latest 5.0.1 module I've been unable to pass in the context.

Cheers,
Lyon

C:\Users\dev> Get-AzureRmContext

Name             : ***********************************
Account          : ***********************************
SubscriptionName : ***********************************
TenantId         : ***********************************
Environment      : AzureCloud

C:\Users\dev> $j = Start-Job -ScriptBlock {
>>         param($context)
>>         Select-AzureRmContext -InputObject $context
>>         Write-Host "**** Some Azure PS command ****"
>>         Get-AzureRmContext | out-host
>>         Get-AzureRmStorageAccount
>>         Write-Host "********"
>>     } -ArgumentList (Get-AzureRmContext)

C:\Users\dev> $j

Id     Name            PSJobTypeName   State         HasMoreData     Location             Command
--     ----            -------------   -----         -----------     --------             -------
3      Job3            BackgroundJob   Completed     True            localhost            ...


C:\Users\dev> Receive-Job -Job $j
**** Some Azure PS command ****

Name             : Default
Account          :
SubscriptionName :
TenantId         :
Environment      :

No account found in the context. Please login using Login-AzureRMAccount.
    + CategoryInfo          : CloseError: (:) [Get-AzureRmStorageAccount], ArgumentException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Management.Storage.GetAzureStorageAccountCommand
    + PSComputerName        : localhost

********

C:\Users\dev>

[blumu]

@ljt91 The Select-AzureRmContext command did not work for me in the end, but I did not have time to investigate further. I think the failure I got was similar to yours. Since I had already migrated all my scripts to take a AzureRmContext parameter and everything was working I decided to keep that workaround instead.