Azure / Azure/azure-rest-api-specs

The sku.tier doesn't take effect while creating app service plan

Open
#9,726 2 comments 0 reactions 0 assignees View on GitHub
Service Attention Web Apps
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 2h
Merged PRs (30d)
424

Description

After tested, seems sku.tier doesn't take effect while creating app service plan. If sku.tier I specified is incorrect, I assume api should throw error, right? Thanks.

Http request:
```
PUT https://management.azure.com/subscriptions/xx-xx-xx-xx/resourceGroups/acctestRG-appservice-test2/providers/Microsoft.Web/serverfarms/demo-app-service-pan

{
"kind": "Windows",
"location": "eastus",
"properties": {
"isXenon": false
},
"sku": {
"name": "F1",
"tier": "Shared",
"size": "F1",
"capacity": 0
},
"tags": {}
}
```

Http response:
```
{
......
"sku": {
"name": "F1",
"tier": "Free",
"size": "F1",
"family": "F",
"capacity": 0
}
}
```

Contributor guide

Open the contributing guide

Research direction

The issue names no repository file or test. Start by locating the App Service serverfarms API specification and comparing its SKU schema with the shown request and response. Done means the expected handling of an invalid or ignored sku.tier is agreed and the corresponding specification behavior is covered by the project's validation or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, openapi
Domain
api, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.