[modify suites] "Missing required property apiVersion" error with apiProfile set to 2017-03-09-profile
See original GitHub issue- apiprofile.json suite
- apiprofile2.json suite
- apiprofile3.json suite - this one works
This template deploys without error. Some give errors, others not.
{ “resource”: “apiprofile2.json”, “owner”: “ARM Template Language Server diagnostics”, “severity”: 4, “message”: “Missing required property "apiVersion"”, “source”: “arm-template (schema)”, “startLineNumber”: 10, “startColumn”: 9, “endLineNumber”: 10, “endColumn”: 10 }
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"apiProfile": "2017-03-09-profile",
"parameters": {
},
"variables": {
},
"resources": [
{
"name": "as",
"type": "Microsoft.Compute/availabilitySets",
"location": "[resourceGroup().location]",
"properties": {
}
},
{
"type": "Microsoft.Storage/storageAccounts",
"name": "[uniquestring(resourcegroup().id)]",
"location": "[resourceGroup().location]",
"sku": {
"name": "Standard_LRS"
},
"kind": "Storage",
"properties": {
}
}
]
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Template fails because of missing API version when using ...
This template is used as a module (not sure if that is important). If the condition solves to false , i.e. the resource...
Read more >Solved: Create ARM Deployment API Error for nested resourc...
Solved: Hi I'm using Flow to Create an Azure ARM Deployment. I initialize two variables, one with the Template and one with the...
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

So it might be fixed by https://dev.azure.com/devdiv/DevDiv/_git/ARM-LanguageServer/pullrequest/247434?_a=files?
We should go ahead and change the suites to 2018-06-01-profile.