Skip to content

[kusto] az kusto cluster update with --sku specified updates unrelated properties #10111

Open

Description

@x-engineering-agent

Source: Azure/azure-cli#33714 (by Mike Keesey (@mkeesey))
Affected extension: kusto (src/kusto/)


<<UNTRUSTED:issue-33714>>

Issue #33714 (by Mike Keesey (@mkeesey))

Title

az kusto cluster update with --sku specified updates unrelated properties

Body

Describe the bug

When running az kusto cluster update --name <name> --subscription <sub> --resource-group <group> --sku name="<sku>" tier="Standard" to migrate compute skus, several unrelated properties of the cluster also were updated.

  1. enableAutoStop switched from false to true
  2. enableDiskEncryption switched from true to false
  3. enablePurge switched from true to false

This is quite unexpected since these properties were not specified, and I do not see anything in the command docs that they are required or have default values.

Related command

az kusto cluster update

Errors

n/a

Issue script & Debug output

n/a - appears to reproduce with any invocation that involves a sku migration.

Expected behavior

I expect the SKU to be updated, but those unconfigured properties to retain their original values.

Environment Summary

azure-cli 2.87.0 *

core 2.87.0 *
telemetry 1.1.0

Extensions:
acr-transfer Unknown
acrtransfer 1.1.0
aks-preview 18.0.0b43
azure-devops 1.0.2
azure-firewall 1.2.2
kusto 0.5.0
nsp 1.0.0
resource-graph 2.1.0
support 2.0.1

Dependencies:
msal 1.36.0
azure-mgmt-resource 24.0.0

Python location '/bin/python3.12'
Config directory '/home//.azure'
Extensions directory '/home//.azure/cliextensions'
Extensions system directory '/usr/lib/python3.12/site-packages/azure-cli-extensions'

Python (Linux) 3.12.9 (main, Jun 2 2026, 15:06:48) [GCC 13.2.0]

Legal docs and information: aka.ms/AzureCliLegal

Additional context

No response

Comments

Comment by @azure-client-tools-bot-prd[bot]

Hi Mike Keesey (@mkeesey),

2.87.0 is not the latest Azure CLI(2.88.0).

If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.

Comment by Mike Keesey (@mkeesey)

Given this would be within the kusto extension, I don't think a minor version bump with the base cli would fix this.
<<END:issue-33714>>

Activity

  1. added
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    customer-reportedIssues that are reported by GitHub users external to the Azure organization.
    Service AttentionThis issue is responsible by Azure service team.
    on Jul 14, 2026
  2. yonzhan commented on Jul 14, 2026

    @yonzhan
    Collaborator

    Thank you for opening this issue, we will look into it.

  3. nithin42 commented on Aug 14, 2026

    @nithin42

    Hi Yong Zhang (@yonzhan) Mike Keesey (@mkeesey),

    I looked into this and traced the root cause to src/kusto/azext_kusto/generated/custom.py in kusto_cluster_update().

    Currently, several optional parameters (enable_auto_stop, enable_disk_encryption, enable_purge, enable_streaming_ingest, etc.) have else: fallback clauses that inject hardcoded False or default values into the update payload whenever they are omitted on the CLI.

    Removing those else: branches ensures az kusto cluster update only sends properties explicitly supplied by the user, preserving all unpassed cluster configurations (matching standard ARM update semantics).

    I have the fix and offline unit tests ready. Would you like me to open a PR for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Auto-AssignAuto assign by botAzure Data ExplorerService AttentionThis issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions