Azure / Azure/AzureCacheForRedis
ARM update fails with 2023-08-01 when setting updateChannel property
- Lenguaje dominante
- PowerShell
- Estrellas
- 12
- Forks
- 17
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Deploying Azure Cache for Redis instance with bicep template below.
The initial deployment works as expected without any issues.
Running deployment again when resource already exists results with error:
> "The unknown resource response code 'NotModified' is encountered."
Removing the line `updateChannel: 'Stable'` fixes the problem. `Stable` is the default either way.
The problem only affects version `2023-08-01` (older versions don't have this property).
```bicep
resource redis 'Microsoft.Cache/redis@2023-08-01' = {
name: 'redis-${uniqueString(resourceGroup().id)}'
location: resourceGroup().location
properties: {
sku: {
name: 'Basic'
family: 'C'
capacity: 0
}
redisConfiguration: {
'maxmemory-reserved': '30'
'maxfragmentationmemory-reserved': '30'
'maxmemory-delta': '30'
}
enableNonSslPort: false
redisVersion: '6.0'
publicNetworkAccess: 'Disabled'
minimumTlsVersion: '1.2'
updateChannel: 'Stable'
}
}
```
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Start by reproducing the second deployment from the issue's Bicep template using Microsoft.Cache/redis API version 2023-08-01 and the updateChannel property. Compare the behavior with that property removed and with older API versions; done means the existing-resource deployment no longer returns the NotModified error while retaining the intended update channel.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- azure, redis
- Área
- cloud, databases
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 30/100