Azure / Azure/azure-rest-api-specs
[BUG][Monitor] RecurrentSchedule.minutes has a confusing type and description
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 6k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
### API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/monitor/resource-manager/Microsoft.Insights/stable/2022-10-01/autoscale_API.json#L612
### API Spec version
2022-10-01
### Describe the bug
origin issue: https://github.com/Azure/azure-sdk-for-python/issues/41643
By the description `A collection of minutes at which the profile takes effect at`, parameter `minutes` should be able to accept multiple values, yet when actually calling the API, it returns message: `The autoscale setting that you provided has an invalid recurrence schedule with invalid count for minutes specified. Specify only one value for minutes.`
### Expected behavior
If `minutes` can only accept one value, then its type should be `integer` instead of `array`, and the description should also be updated.
Or the service should support `minutes` with multiple values.
### Actual behavior
`minutes` clarified to be a collection, yet it can only accept one value.
### Reproduction Steps
calling API `https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Insights/autoscalesettings` with property `recurrence` as:
```
{"frequency": "Week", "schedule": {"timeZone": "UTC", "days": ["Monday"], "hours": [0, 2], "minutes": [1, 2]}}
```
### Environment
_No response_
Contributor guide
Research direction
Start with specification/monitor/resource-manager/Microsoft.Insights/stable/2022-10-01/autoscale_API.json around line 612 and reproduce the request against the autoscale settings endpoint using the minutes values shown. Confirm whether the service accepts one or multiple minutes, then ensure the API specification's type and description match the verified behavior.
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