expressionEvaluationOptions is not in completion list for nested template properties
See original GitHub issue- Use this template:
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
},
"resources": [
{
"type": "Microsoft.Resources/deployments",
"apiVersion": "2019-10-01",
"name": "nestedTemplate1",
"properties": {
}
}
]
}
- Put cursor inside properties and hit CTRL+SPACE
!) completion list should include
expressionEvaluationOptionsbut doesn’t
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
expressionEvaluationOptions property missing from 2019-10 ...
expressionEvaluationOptions is not in completion list for nested template properties microsoft/vscode-azurearmtools#714.
Read more >How to link resources in a nested ARM template?
This is my template so far. Both the dependsOn and subnets.properties.id links are not working. { "$schema": "https://schema ...
Read more >ExpressionEvaluationOptions interface - Microsoft Learn
Specifies whether template expressions are evaluated within the scope of the parent template or nested template. In this article. Properties; Property ...
Read more >Learn Modules In Azure Bicep - Basics To Advanced, How It ...
In general, Bicep language is the future of ARM templates in Azure. ... then nested template's resources are treated as in complete mode, ......
Read more >ARM Templates Modularization using Nested and Linked ...
Modularization of ARM templates is one of the key concepts for delivering reusable and easy to maintain components for your application ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Right, the Resource Manager API version 2020-06-01 supports expressionEvaluationOptions property. Looks like the changes are reflected in the VS Code extension now. PR link for reference: https://github.com/Azure/azure-rest-api-specs/pull/11174/files
That makes sense, the api’s should be backwards compatible. Good to close @StephenWeatherford?