Octostash not finding variables in included variable library for Azure deployment

I have a deployment which deploys an ASP.Net website and one of the steps is a deployment of an Azure worker role. Each of these has variable replacement step. We include a library variable set which includes common values. The variable replacement works perfectly in the web deploy. However, in the Azure deploy, variables from the included set are not found:

Parsing file 'C:\Octopus\Work\20160428172243-12\LocalContent\Azure.Worker\approot\Azure.Worker.dll.config' with Octostache returned the following error: `The following tokens were unable to be evaluated: '#{WebContext}', '#{ManagementContext}'

This error doesn’t occur if I copy the variable to the project variables (the variable is replaced as expected), leading me to think there is an issue with Azure deployments and library variable sets.

Are library variable sets supported in Azure deployments?

Hi Rory,

Thanks for getting in touch! Generally scoping is the culprit in these scenarios. A way to figure out what is going on is to turn on some variable logging.
Then if you could send a full deployment log I should be able to tell you whats going on:


I have the full log with variable output which I could send privately. From my reading of it, the variables do indeed have the values, as they are not only in the log, but in fact they are deployed in the first step of the web being deployed in the same deployment.

Hi Rory,

Send it through to support at octopus dot com and I’ll take a look.


Sent. Thank you!