Ambiguity under 'Pipeline resource metadata as predefined variables' about azure-devops-yaml-schema HOT 4 OPEN

@WilliamAntonRohm @steved0x -- Thanks! I found this other section about pipeline resource variables that specifically say: 'Pipeline resources variables are only available at runtime,' which does explain why ${{ if eq(variables[resources.pipeline.<Alias>.sourceBranch], 'refs/heads/master') }} does not get evaluated as expected.

Would be great if that line could be added to the documentation under Pipeline resource metadata as predefined variables too.

I will also post the question on Azure DevOps Services to see if there is a workaround in the meanwhile.

from azure-devops-yaml-schema.

ADO support confirmed that the resource variables will not be available in a template expression, even though they are predefined variables. This is because resource variables are only available at runtime.

That information should definitely be included under Pipeline resource metadata as predefined variables, as it is under Pipeline resource variables.

from azure-devops-yaml-schema.

@lydiacheah -- Lydia, thank you for your thorough feedback. Please consider these resources:

• Azure DevOps Services
• Azure DevOps on Stack Overflow

@steved0x -- Steve, please look into this issue.

from azure-devops-yaml-schema.

@lydiacheah -- Lydia, thank you for your thorough follow-up.

from azure-devops-yaml-schema.