We use Octopus to deploy Azure Resource Manager templates, this has all been working fine. Recently we have updated our templates to use Azure Key Vault for storing protected variables, as per this update from the Azure team - https://azure.microsoft.com/en-gb/blog/keyvault-support-for-arm-templates/
This works when deploying with Visual Studio, but not when using Octopus, this complains about the parameters that use the vault being null. I have updated Octopus to 3.3.6 and have installed the latest Azure PowerShell cmdlets and configured Octopus to use them.
Sorry for the delay here. When you first mentioned that the “Key Vault” was usable from ARM templates, I didn’t even know it was possible. And now I know why: It was introduced in the Azure SDK that was released 8 days ago!
So yeah, at the current version of Octopus we don’t support it. But its definitely something that we’ll look into supporting when we update the Azure binaries we use in Octopus, which might happen rather sooner than later.
In the meantime, I’ve added a uservoice suggestion so the community can add votes to it to let us know they want this.
Hi, I just wanted to check in and see if there there was any update on when we might see this working in Octopus? Our ARM scripts all use key vault at the moment, and we want to move them into Octopus so it would be good to know if this is likely to be coming soon, or if it’s going to be a while and it’s worth my time update the scripts to not use key vault.