ARM update fails with 2023-08-01 when setting updateChannel property

Open

#13 opened on Nov 17, 2023 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 30/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: azure, redis
Domain: cloud, databases

Research direction

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.

Written by the indexing model from the issue text.

Description

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).

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'
  }
}

Dominant language: PowerShell
Stars: 12
Forks: 17
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
fix(mcp): `permanently_delete_cloud_{source,destination,connection}` lack `workspace_id` param, unusable without a default workspace Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

airbytehq/PyAirbyte#1201 · Opened Sep 21, 2026
[BUG] Route53Resolver: CreateResolverEndpoint requires IpAddressRequests, but the AWS member is IpAddresses, so no SDK client can call it Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

floci-io/floci#4108 · Opened Sep 21, 2026
wm_gcp_parse_output underflows its heap buffer by one byte Open

level/task module/gcp type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

wazuh/wazuh#39525 · Opened Sep 21, 2026
[Bug]: aws_lb_listener silently ignores tcp_idle_timeout_seconds on TCP_UDP listeners Open

bug needs-triage service/elbv2

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

hashicorp/terraform-provider-aws#50100 · 1 comment · Opened Sep 21, 2026

More Cloud issues