New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Calamari Microsoft Azure packages (for ARM steps) #3637

Closed
thebigmoosey opened this Issue Jul 6, 2017 · 12 comments

Comments

Projects
None yet
10 participants
@thebigmoosey

thebigmoosey commented Jul 6, 2017

We need to update the Microsoft.Azure.Management.Resources nuget packages we're currently using in Calamari, as customers are relying on Powershell workarounds to bypass limitations with the library currently bundled.

As part of this ticket, we should also see if there's a way we can allow users to specify their own version of these libs (similar to extensions and/or the way we allow custom PowerShell modules) so they can use the latest and greatest and not be stuck with whatever Calamari has bundled.

Source: http://help.octopusdeploy.com/discussions/problems/55689

@thebigmoosey

This comment has been minimized.

Show comment
Hide comment
@jimmcslim

This comment has been minimized.

Show comment
Hide comment
@jimmcslim

jimmcslim Aug 10, 2017

I have been bitten by this issue as well so it would be great if this was resolved soon!

jimmcslim commented Aug 10, 2017

I have been bitten by this issue as well so it would be great if this was resolved soon!

@chudsonwr

This comment has been minimized.

Show comment
Hide comment
@chudsonwr

chudsonwr Oct 13, 2017

Me too, the API in use by Octopus '2014-04-01-preview' is extremely old...please update to the latest

chudsonwr commented Oct 13, 2017

Me too, the API in use by Octopus '2014-04-01-preview' is extremely old...please update to the latest

@thebigmoosey

This comment has been minimized.

Show comment
Hide comment
@timpoth

This comment has been minimized.

Show comment
Hide comment
@timpoth

timpoth Dec 20, 2017

bump on this.

timpoth commented Dec 20, 2017

bump on this.

@gettek

This comment has been minimized.

Show comment
Hide comment
@gettek

gettek Jan 8, 2018

Double bump on this

gettek commented Jan 8, 2018

Double bump on this

@shaunmarx

This comment has been minimized.

Show comment
Hide comment
@shaunmarx

shaunmarx Feb 5, 2018

Please note that if you are using an ASE you may get an exception with a message such as Requested value 'Isolated' was not found.

shaunmarx commented Feb 5, 2018

Please note that if you are using an ASE you may get an exception with a message such as Requested value 'Isolated' was not found.

@StephenShamakian

This comment has been minimized.

Show comment
Hide comment
@StephenShamakian

StephenShamakian Feb 5, 2018

Thanks @shaunmarx the ASE problem is affecting us. I would love to see these bundles get updated (a 2014 nuget package seems like it should probably be updated) as a quick fix. then maybe down the road add the ability to choose which assembly to use down the road.

StephenShamakian commented Feb 5, 2018

Thanks @shaunmarx the ASE problem is affecting us. I would love to see these bundles get updated (a 2014 nuget package seems like it should probably be updated) as a quick fix. then maybe down the road add the ability to choose which assembly to use down the road.

@StephenShamakian

This comment has been minimized.

Show comment
Hide comment
@StephenShamakian

StephenShamakian Feb 22, 2018

@shaunmarx @thebigmoosey Any ETA for updated Azure APIs?

StephenShamakian commented Feb 22, 2018

@shaunmarx @thebigmoosey Any ETA for updated Azure APIs?

@thebigmoosey

This comment has been minimized.

Show comment
Hide comment
@thebigmoosey

thebigmoosey Feb 22, 2018

Hi everyone, thanks for your feedback and patience on this. We're actively working on integrating the latest Azure .NET libraries to fix these problems and have plans to release these updates in April.

Unfortunately it's not as simple as updating a NuGet package as a quick fix, as Microsoft has deprecated the library we are currently using from 2016 (which is returning those messages about 2014-04-01-preview in ARM templates) and updating to the latest of that does not fix the problems, so we're in the process of migrating to the newer libraries that support the latest SDK and ARM templates.

^ This has been further complicated by several things:

  1. the new Azure libraries having a dependency on .NET452, so a bunch of other dependencies in Octopus and Calamari.Azure that were expecting .NET451 are under review also and will need to be updated.
  2. the new Azure libraries do not appear to support non-interactive logins with Management Certificate accounts, which Octopus currently supports for deploying Web Apps (we've had no problem with the Service Principal accounts side-of-things), so we're working through those issues as well - we may need to include both the older libraries for dealing with Management Certificate accounts and the newer libraries for handling Service Principal accounts (we've reached out to Azure in their forums and directly on GitHub, but haven't heard back as yet).

TLDR; much has changed with Azure and it's taking time to de-tangle both the SDKs and PowerShell cmdlets in both Octopus and Calamari.Azure, but we're making good progress.

thebigmoosey commented Feb 22, 2018

Hi everyone, thanks for your feedback and patience on this. We're actively working on integrating the latest Azure .NET libraries to fix these problems and have plans to release these updates in April.

Unfortunately it's not as simple as updating a NuGet package as a quick fix, as Microsoft has deprecated the library we are currently using from 2016 (which is returning those messages about 2014-04-01-preview in ARM templates) and updating to the latest of that does not fix the problems, so we're in the process of migrating to the newer libraries that support the latest SDK and ARM templates.

^ This has been further complicated by several things:

  1. the new Azure libraries having a dependency on .NET452, so a bunch of other dependencies in Octopus and Calamari.Azure that were expecting .NET451 are under review also and will need to be updated.
  2. the new Azure libraries do not appear to support non-interactive logins with Management Certificate accounts, which Octopus currently supports for deploying Web Apps (we've had no problem with the Service Principal accounts side-of-things), so we're working through those issues as well - we may need to include both the older libraries for dealing with Management Certificate accounts and the newer libraries for handling Service Principal accounts (we've reached out to Azure in their forums and directly on GitHub, but haven't heard back as yet).

TLDR; much has changed with Azure and it's taking time to de-tangle both the SDKs and PowerShell cmdlets in both Octopus and Calamari.Azure, but we're making good progress.

@mjhilton

This comment has been minimized.

Show comment
Hide comment
@mjhilton

mjhilton Apr 5, 2018

This one just bit me as well @thebigmoosey. Crafted an epic, beautiful nested template which works great via local Powershell, then whack it in Octo and hit a big red wall of text 😭

Working around it using an Azure Script step calling New-AzureRmResourceGroupDeployment, and a project variable of Octopus.Action.Azure.UseBundledAzurePowerShellModules = false, but not a fan of that vs the proper ARM Step Template.

Looking forward to seeing this one fixed 😊

mjhilton commented Apr 5, 2018

This one just bit me as well @thebigmoosey. Crafted an epic, beautiful nested template which works great via local Powershell, then whack it in Octo and hit a big red wall of text 😭

Working around it using an Azure Script step calling New-AzureRmResourceGroupDeployment, and a project variable of Octopus.Action.Azure.UseBundledAzurePowerShellModules = false, but not a fan of that vs the proper ARM Step Template.

Looking forward to seeing this one fixed 😊

@octoreleasebot

This comment has been minimized.

Show comment
Hide comment
@octoreleasebot

octoreleasebot May 11, 2018

Release Note: Updated Azure SDK dependencies to latest. Updated Azure PowerShell Modules to v5.7.0.

octoreleasebot commented May 11, 2018

Release Note: Updated Azure SDK dependencies to latest. Updated Azure PowerShell Modules to v5.7.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment