stages - Property ${{ each env in parameters.paramName }} is not allowed

[mmcossu]

file: azure-pipelines.yml

 1. parameters:
 2.   - name: deployTo
 3.     displayName: Deployment Environments
 4.     type: stringList
 5.     values:
 6.       - development
 7.       - test
 8.       - production
 9.     default: []
10. 
11. stages:
12.   - ${{ each env in parameters.deployTo }}:
13.       - stage: ${{ env }}
14.         jobs:
15.           # rest of code

line 12 error:
Property ${{ each env in parameters.deployTo }} is not allowed.yaml-schema: Azure Pipelines(513)

the pipeline executes correctly.
schema must be therefore incorrect.
schema should allow for a loop just after stages if the pipeline is correctly executed by Azure DevOps.

fix the schema.

[winstliu]

Azure Pipelines(513) indicates that the wrong language is selected in VS Code. In the status bar (or Change Language Mode in the Command Palette), make sure the active language is Azure Pipelines, NOT YAML.

[mmcossu]

Extensione installed:

language selected:

error:

reopen issue

and indicate where the schema is located so that i can give a look and try contribute with a PR

[winstliu]

Huh, interesting. The schema itself doesn't support compile-time expressions; I had to work that into the language service at https://github.com/microsoft/azure-pipelines-language-server. The error you're seeing is still the same?

[mmcossu]

Same error, yes

[coolhome]

This happens when azure pipeline language is the preferred language and the original yaml extension adds a json schema. It's hard to get azure pipelines to stick especially when ansible extension is installed.

[mmcossu]

hi @coolhome, I apologize but I'm not entirely following.
I'm not sure the preferred language for YAML is the one for the Azure Pipeline, unless it's a mechanism applied by default by the Azure Pipeline Extension.
Is there a way to check it precisely?

Having said that, what I'm experiencing is the behavior for which:

• the azure pipeline json schema is not applied when selecting the Azure Pipeline language
  Are you saying that the original schema has some kind of priority over the azure pipeline schema?

Is there a way to see which schema is loaded when selecting the language?