Azure / Azure/azure-rest-api-specs
Microsoft.HybridCompute@2022-03-10 Unexpected 400 returned from service
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
swagger link: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/hybridcompute/resource-manager/Microsoft.HybridCompute/stable/2022-03-10/HybridCompute.json
API Example:
PUT https://management.azure.com/subscriptions/{SID}/resourceGroups/yunliutesthyc/providers/Microsoft.HybridCompute/machines/myMachine?api-version=2022-03-10
Json Body:
{
"location": "west europe",
"properties": {
"VmId": "vm-221014143600135524",
"locationData": {
"name": "Redmond"
},
"clientPublicKey": "string"
},
"identity": {
"type": "SystemAssigned"
}
}
Returns:
--------------------------------------------------------------------------------
│ RESPONSE 400: 400 Bad Request
│ ERROR CODE: HCRP400
│ --------------------------------------------------------------------------------
│ {
│ "code": "HCRP400",
│ "message": "The request does not have sufficient information to complete the operation. Missing or invalid properties: VmId",
│ "target": "{sid}/yunliutesthyc2/testacchycmachine"
│ }
│ --------------------------------------------------------------------------------
Contributor guide
Research direction
Open specification/hybridcompute/resource-manager/Microsoft.HybridCompute/stable/2022-03-10/HybridCompute.json and compare its HybridCompute machine definition with the PUT example and HCRP400 response. Verify how VmId is documented and supplied in the request; done means the specification and example accurately reflect the service's required VmId input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100