Azure / Azure/azure-rest-api-specs
Multiple specs error with latest autorest due tag config multiple defination
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 424
Description
These specs:
[specification/softwareplan/resource-manager/readme.md](https://github.com/Azure/azure-rest-api-specs/blob/d9cf7c7ed3d674ebd482836e82b274014245ae67/specification/softwareplan/resource-manager/readme.md)
and
[specification/desktopvirtualization/resource-manager/readme.md](https://github.com/Azure/azure-rest-api-specs/blob/d9cf7c7ed3d674ebd482836e82b274014245ae67/specification/desktopvirtualization/resource-manager/readme.md)
and
[specification/iotcentral/resource-manager/readme.md](https://github.com/Azure/azure-rest-api-specs/blob/d9cf7c7ed3d674ebd482836e82b274014245ae67/specification/iotcentral/resource-manager/readme.md)
and
[specification/hybriddatamanager/resource-manager/readme.md](https://github.com/Azure/azure-rest-api-specs/blob/d9cf7c7ed3d674ebd482836e82b274014245ae67/specification/hybriddatamanager/resource-manager/readme.md)
fail when processed with autorest 3.1.0-dev.2.
Discussions with @timotheeguerin suggests that they are issues in the swagger redefining tags:
`it used to test release_2 but now is testing release_1 with that $ref as an attribute`
Builds showing issue:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=748819&view=logs&j=1a6ae1a5-56d5-51f8-8f8d-f67115b54b1a&t=937f187a-1519-5cb7-77a5-47832257e788
https://dev.azure.com/azure-sdk/public/_build/results?buildId=751474&view=logs&j=ac074fc7-7a1e-5636-a7ea-9c59e123a9ef&t=79ef76a9-b720-5417-f045-9a3cbd25ad16
Contributor guide
Research direction
Start with the four linked resource-manager/readme.md files and reproduce their failures using autorest 3.1.0-dev.2. Review the linked Azure DevOps build logs and the discussion about redefined swagger tags, then verify that all four specifications process successfully without the reported tag-configuration errors.
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
- Mostly clear
- Newbie friendliness
- 35/100