Handle assembly already loaded errors in deploy stress test script

[benbp]

This issue has been showing up recently: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1103685&view=logs&j=38a05975-7697-5434-099a-d7b3d4012883&t=b1e71580-9408-50be-13a0-b0783b8cb008&l=57

Installing module az with min version 6.4.0 from https://www.powershellgallery.com/api/v2
Using module Az with version 6.4.0.
Import-Module : Assembly with same name is already loaded
At /home/vsts/.local/share/powershell/Modules/Az/6.4.0/Az.psm1:113 char:1
+ Import-Module Az.Aks -RequiredVersion 2.4.0 -Global
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (:) [Import-Module], FileLoadException
+ FullyQualifiedErrorId : FormatXmlUpdateException,Microsoft.PowerShell.Commands.ImportModuleCommand

[benbp]

/azp run Stress Test Release

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[weshaggard]

If this is a common error we should consider adding a helper function for importing.

[weshaggard]

Is this a real problem? We should only be importing it if it isn't already loaded.

[benbp]

@weshaggard I'm not quite sure what's going on here, or why it seems to be only affecting this pipeline and not ALL pipelines that use this. I thought of this as a short term workaround but I really would like to understand the root issue here.

[benbp]

@weshaggard turns out it doesn't work anyway: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1108561&view=logs&j=38a05975-7697-5434-099a-d7b3d4012883&t=b1e71580-9408-50be-13a0-b0783b8cb008&l=58

[weshaggard]

I'm not sure why it isn't correctly detecting the loaded module but it looks like you aren't using this in a normal powershell step but instead as part of some Azure CLI step is there a reason for that?

[benbp]

I'm not sure why it isn't correctly detecting the loaded module but it looks like you aren't using this in a normal powershell step but instead as part of some Azure CLI step is there a reason for that?

Now I'm not so sure why I even added this as a dependency at all. We don't use the Az cmdlets in this script...

[benbp]

@weshaggard updated the PR to check for azure cli not Az and added some more helpful prompts that don't require going to the README when tools aren't installed (automatically installing them is not easy given cross-platform usage).

I have been using the Azure CLI step in order to pass through the azure service connection to the azure cli usage in the script.

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[benbp]

/azp run Stress Test Release

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[ghost]

Hello @azure-sdk!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[benbp]

/check-enforcer override