Azure / Azure/azure-rest-api-specs
ContainerGroups_Delete says it returns a ContatinerGroup instance for 200 response
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
EX:
https://github.com/Azure/azure-rest-api-specs/blob/c69314600112f589c24cc2054ccff990b4a86897/specification/containerinstance/resource-manager/Microsoft.ContainerInstance/stable/2018-10-01/containerInstance.json#L280-L285
The examples show it with an empty response, similar to other APIs. Not sure if changing that is a breaking change, but it looks like it is in all versions of the API.
Contributor guide
Research direction
Open specification/containerinstance/resource-manager/Microsoft.ContainerInstance/stable/2018-10-01/containerInstance.json around lines 280-285 and compare the 200 response with the nearby API examples that show an empty response. Check whether the same return definition appears in the other API versions mentioned by the issue. Done means the specification consistently describes the actual empty 200 response without an unintended ContainerGroup instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100