Azure / Azure/bicep

'originResponseTimeoutSeconds' does not work for 'Standard_Microsoft' SKU CDN profile

Open
#6,175 2 comments 0 reactions 0 assignees View on GitHub
provider bug
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

**Bicep version**
run `bicep --version` via the Bicep CLI, `az bicep version` via the AZ CLI or via VS code by navigating to the extensions tab and searching for Bicep

`Bicep CLI version 0.4.1272 (a69022dd2c)`

**Describe the bug**
The CDN will give 503 when a request takes longer than 30 seconds. The bicep interface indicates that this can be adjusted, however it does not appear to have been adjusted after deployment for 'Standard_Microsoft' SKU.

Can we confirm that it indeed does not work for `Standard_Microsoft` even though the interface allows it, or does it not get added due to a bug?

The interface is shared with a lot of other CDN SKU, that do have this setting changed after deployment.

**To Reproduce**
1) Run template

```
resource frontDoorProfile 'Microsoft.Cdn/profiles@2021-06-01' = {
name: 'my-profile-frontdoor'
location: 'global'
sku: {
name: 'Standard_AzureFrontDoor'
}
properties: {
originResponseTimeoutSeconds: 120
}
}

resource classicProfile 'Microsoft.Cdn/profiles@2021-06-01' = {
name: 'my-profile'
location: 'global'
sku: {
name: 'Standard_Microsoft'
}
properties: {
originResponseTimeoutSeconds: 120
}
}

```
2) Inspect results via rest or export template from azure
3) Find that the property is not set for `my-profile` and is set for `my-profile-frontdoor`

**Additional context**
In an old answered question by MSFT it is stated that standard CDN does not provide this setting.
https://docs.microsoft.com/en-us/answers/questions/76487/increase-origin-first-response-read-timeout-length.html

However, this bicep interface suggests it does. And the interface on api level 2021-06-01 is available after the question so it could have been added later.

Contributor guide

Open the contributing guide

Research direction

Deploy the two Microsoft.Cdn/profiles@2021-06-01 resources from the issue, using the Bicep CLI or Azure CLI, then inspect both results through REST or an exported template. Compare originResponseTimeoutSeconds for Standard_Microsoft and Standard_AzureFrontDoor; done means determining whether the property is unsupported for Standard_Microsoft or whether Bicep accepts it incorrectly.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.