Azure / Azure/azure-rest-api-specs

Trying to use apiProfile 2018-03-01-hybrid got no support for Microsoft.Compute/virtualMachines

Open
#3,629 1 comment 0 reactions 0 assignees View on GitHub
Compute Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 2h
Merged PRs (30d)
424

Description

Doing New-AzureRmResourceGroupDeployment on PS, the template validates ok with apiProfile [2018-03-01-hybrid](https://github.com/Azure/azure-rest-api-specs/blob/master/profile/2018-03-01-hybrid.json) but when deploying a VM resource there is no valid apiVersion. For what it seems, there is support for apiVersion [2017-03-30](https://github.com/Azure/azure-rest-api-specs/blob/master/profile/2018-03-01-hybrid.json#L35) (which appears valid), but the API keeps responding:
> The api-profile '2018-03-01-hybrid' for the template does not match any valid api-version for the resource type 'Microsoft.Compute/virtualMachines'. Either explicitly specify the api-version for the resource or specify the correct api-profile for the template

Thanks!

Contributor guide

Open the contributing guide

Research direction

Start with profile/2018-03-01-hybrid.json, especially the Microsoft.Compute/virtualMachines entry linked in the report, and reproduce the New-AzureRmResourceGroupDeployment validation and deployment behavior. Check how the profile's listed API versions are matched to the resource type; done means the profile accepts a valid version for virtualMachines and the reported mismatch no longer occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
api, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.