Configuring the version of the Azure PowerShell modules

Legacy Uncategorised
1

Hi,
We have a step that uses the old version of azure powershell (using the code at: http://docs.octopusdeploy.com/display/OD/Configuring+the+version+of+the+Azure+PowerShell+modules)
which has worked fine until the upgrade. Since the upgrade to 3.3 using this no longer appears to alter the version of azure powershell used. Has the --azurePowerShellModule command been removed?

Thankyou
Dave

2

Hi Dave,
We are sorry to hear that you are having such problems with the new 3.3 release. As you are probably aware there were some big changes to the way we handle Azure connections now that we provide side-by-side support for Azure Service Management (ASM) and the Azure Release Manager (ARM) authentication. As a result, the process for configuring the Azure context in PowerShell scripts has undergone some changes.

We have introduced a new variable Octopus.Action.Azure.UseBundledAzurePowerShellModules which instead enables you to disable the default module auto loading and allows you to load the required modules in your own scripts to ensure the right versions are used. That being said I can see that some of the documentation on this topic and these changes are lacking. I will also need to do some further investigations into the changes to confirm if there is any other way we can get the old behaviour working again.

I’m sorry I am unable to give an immediate solution to get your old scripts working exactly as-is again however will update you as soon as I have more information.
Thank you for your patience,
Rob

3

Hi Again Dave,
After talking to the developer who worked on this feature, I can confirm that the correct approach should be to include the Octopus.Action.Azure.UseBundledAzurePowerShellModules variable in your project variables and set it to false. This will then prevent the azure modules that we include in Calamari from being used and instead allow you to use your own. So long as the Azure modules that you would prefer to be invoked are available to the PowerShell context then they should get picked up instead.

We will update documentation around these changes to ensure that this confusion does not happen again for other users.

Please let me know if you have any further questions,
Cheers,
Rob

4

I have tried with the variable set to false and can confirm that this has worked.
Thankyou