Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Output variables fail to evaluate for Azure account fields #3724
If you try to use an output variable as a custom expression on an Azure account field, it fails when you try to deploy the release:
For example, if you setup a script step called "set output var" that sets the output variable:
Then reference this output variable as a custom expression on an Azure step, as follows:
When you deploy the release, you receive this error message:
We also tried to "trick it" by creating a project-level variable that referenced the output variable instead, then using the project-variable in the Azure step, but the same error occurs.
We'll need to investigate why the account variable is not properly evaluating output variables, because there's a valid use case for switching between different Azure accounts in your deployments (based on scripting logic to set output variables).
I reported the issue linked above (#3856).
Is the piece of code that handles these principals closed source?
I'm happy to take a look and see if I can Pull Request a fix for this issue, as we have had to opt for "Blue/Green" approach in work to deploy to Azure in parallel, and that lifecycle doesn't accurately describe the cloud region.
referenced this issue
Dec 12, 2017
@ColinM9991 We agree, and sorry we can't be of more help in terms of estimates, but this issue is in our pipeline and will be actioned by our cloud team.
We're currently reviewing the whole concept of "Cloud Regions". Our specs repo for Resources discusses the directions we're considering for a better cloud-first approach (this is an area that touches on accounts), so in terms of priorities, these variable issues will be better solved once we understand where cloud regions fit in this new model.