Azure / Azure/azure-rest-api-specs
Static Site with `Free` sku doesn't support `identity` anymore?
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 395
Description
A `PUT` request against the static site endpoint (at least for 2019-12-01-preview and 2021-02-01) with below payload fails recently:
```json
{
"identity": {
"type": "None"
},
"location": "West Europe",
"tags": {},
"properties": {
},
"sku": {
"name": "Free",
"tier": "Free"
}
}
```
With error:
```
{
"Code": "BadRequest",
"Message": "SkuCode 'SKU' is invalid.",
"Target": null,
"Details": [
{
"Message": "SkuCode 'SKU' is invalid."
},
{
"Code": "BadRequest"
},
{
"ErrorEntity": {
"ExtendedCode": "55925",
"MessageTemplate": "SkuCode '{0}' is invalid.",
"Parameters": [
"SKU",
"Free"
],
"Code": "BadRequest",
"Message": "SkuCode 'SKU' is invalid."
}
}
],
"Innererror": null
}
```
While if change the sku to `Standard`, or remove the `identity` block, it works. Did the service team remove the support of `identity` from the `Free` SKU?
Contributor guide
Research direction
Start with the static site PUT endpoint and compare the 2019-12-01-preview and 2021-02-01 payloads shown here, especially the identity block and Free SKU. Check the relevant Azure REST specification and service behavior to determine whether this combination is supported; done means the support status and any required specification change are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100