Azure / Azure/azure-rest-api-specs

`migrate@2020-01-01`: `VMwareRunAsAccount` lack `appliancename` definition

Open
#24,712 1 comment 0 reactions 0 assignees View on GitHub
Migrate Service Attention
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/d71132a3e8bf8ad22ab77991805e033ed1b66dff/specification/migrate/resource-manager/Microsoft.OffAzure/stable/2020-01-01/migrate.json#L4476

the service will return appliance name but it has not been defined in Swagger.

As https://github.com/Azure/azure-rest-api-specs/issues/24711, there is no way to get runAsAccount with a specified applianc,

Contributor guide

Open the contributing guide

Research direction

Open specification/migrate/resource-manager/Microsoft.OffAzure/stable/2020-01-01/migrate.json around line 4476 and inspect the VMwareRunAsAccount definition. Compare the service response described in the issue with the Swagger schema, then confirm that appliancename is defined and that runAsAccount can be retrieved for a specified appliance.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.