[Task] Remove confusing "Command group 'config' is experimental" warning #34186

Activity

1. Alex Wang (Alex-AZPS)

   added

   bugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.

   on Oct 8, 2026
2. microsoft-github-policy-service

   added

   Auto-AssignAuto assign by botAuto assign by bot

   Configureaz configure/configaz configure/config

   Azure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI team

   questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

   act-codegen-extensibility-squad

   on Oct 8, 2026
3. yonzhan commented on Oct 8, 2026

   

   Yong Zhang (yonzhan)

   on Oct 8, 2026

   Collaborator

   More actions

   Thank you for opening this issue, we will look into it.
4. Alex Wang (Alex-AZPS)

   added

   act-quality-productivity-squad

   and removed

   act-codegen-extensibility-squad

   questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

   on Oct 8, 2026
5. microsoft-github-policy-service commented on Oct 8, 2026

   

   microsoft-github-policy-serviceBot

   on Oct 8, 2026 – with Microsoft GitHub Policy Service

   Contributor

   More actions

   🔔 Routing this issue to @Azure/act-quality-productivity-squad.
6. Alex Wang (Alex-AZPS)

   assigned

   Ethan Yang (necusjz)

   on Oct 8, 2026
7. Yong Zhang (yonzhan)

   modified the milestones: September 2026 (2026-09-01), November 2026 (2026-11-03) on Oct 8, 2026
8. x-engineering-agent commented on Oct 8, 2026

   

   x-engineering-agentBot

   on Oct 8, 2026 – with X Engineering Agent

   Contributor

   More actions

   Bug Analysis

   The report provides a command, the exact unwanted warning, expected behavior and repeatable steps. No additional environment information is needed to investigate this metadata issue. The similarity service returned no candidate duplicates.

   Affected module: src/azure-cli/azure/cli/command_modules/config/

   Source evidence: At dev revision ef09fd936278dd048f7368b6b1043627ae18c99a, config/commands.py:13-16 registers the entire config group with is_experimental=True, covering set, get and unset. The config param-persist group independently declares is_experimental=True at lines 18-22. This explains the scope of the reported warning; this analysis is based on source inspection, not an executed reproduction.

   Reported behavior: az config set core.enable_broker_on_windows=false emits the group-level experimental warning. The requested result is warning-free ordinary configuration commands, without changing broker settings or configuration semantics.

   Use this EXACT PR title: [Config] Fix #34186: az config: Remove the blanket experimental warning

   Requirements for the fix:

   • Target Azure/azure-cli branch dev and keep the implementation in the handwritten config module. Do not alter the separate configure module.
   • Remove the blanket experimental marking from the ordinary config group. Preserve the explicit experimental status of config param-persist and any genuinely experimental child command or parameter. Do not globally suppress warnings or modify the shared command framework to hide this warning.
   • Preserve existing set/get/unset behavior, output, persistence, errors and exit status. Do not change authentication/broker defaults or user configuration as part of this fix.
   • Extend src/azure-cli/azure/cli/command_modules/config/tests/latest/test_config.py with regression coverage that checks actual warning behavior for config set, config get and config unset, not just a metadata mapping. Use isolated temporary configuration and verify the existing configuration results as well.
   • Cover preservation of the narrower config param-persist warning using the existing test_param_persist.py suite or a focused command-loading regression. Keep existing parameter-persistence behavior unchanged.
   • Run the repository's existing focused config test suites in the isolated Foundry implementation job and report the exact results. These commands are local configuration operations; no Azure credentials or service resources should be needed. Update directly affected help or customer-facing history notes if required, without manually changing generated history files.

   Mandatory Codegen execution protocol

   Before editing implementation files, determine whether the affected config command is AAZ-generated. Files under aaz/<profile>/ are generated output and must never be patched directly, including by an AI agent. Check out Azure/aaz beside Azure/azure-rest-api-specs, Azure/aaz-dev-tools, and the downstream repository. API-schema defects start in the specification; command naming, grouping, arguments, API-version selection, help, and examples belong in the durable Azure/aaz command model; non-modelable client behavior belongs in a handwritten subclass or wrapper in custom.py, registered from commands.py. X Engineering Agent creates and promotes the corresponding durable Azure/aaz source pull request before it promotes downstream generated output.

   Follow the Azure CLI repository's Codegen workflow and the aaz-dev setup documentation. Set up the checked-out repositories with azdev setup. Use generate only when importing or redesigning command models from Swagger/TypeSpec. For an existing module whose durable Azure/aaz model has been updated, render that model with regenerate:

   aaz-dev cli regenerate --name config --cli-path <azure-cli>
   
   # New/imported command model only:
   aaz-dev cli generate --spec <specification-name> --module config

   You MUST actually run the generator; do not merely describe it or imitate its output. If the AAZ/specification checkout, local source change, credentials, or generator is unavailable, stop and report the blocker instead of editing generated files. Inspect _aaz_info provenance and the complete regenerated diff, then run focused azdev style, azdev linter, and azdev test validation. For an extension, also update its version and HISTORY.rst, preserve azext_metadata.json compatibility, and let release automation update src/index.json.

   PR title & description format (required)

   This repo enforces a PR format (guide). Please author the PR exactly as follows or CI's Check the Format of Pull Request Title and Content will fail.

   Use this EXACT PR title (copy verbatim, do not reword):

   [Config] Fix #34186: `az config`: Remove the blanket experimental warning
   

   Keep the backticks around the command and the Fix #34186: prefix. You may only adjust the wording after the command (the final summary) if the fix changes; the [Config] prefix, issue link, and backticked command must stay.

   Description — follow the PR template and fill in:

   • Link the issue — start the Description with a closing keyword so the PR auto-links and closes it: Fixes #34186.
   • Related command — the az ... command this affects.
   • Description (mandatory) — why the bug happens, what you changed, and the resulting behavior.
   • Testing Guide — example command(s) showing the fix works.
   • History Notes — leave the title to drive the history note, or add extra lines in the same format (component in brackets + the command in backticks), e.g. [Config] `az <command>`: <note>.
   • Keep the template checklist and tick the items you've satisfied.

   Posted by x-engineering-agent (Fixer)
9. Aditya Pujara (a0x1ab)

   added 2 commits that reference this issue on Oct 8, 2026

   [Config] Fix Azure#34186: `az config`: Remove the blanket experimenta…

   ...

   This issue will close once commit 3aa869e is merged into the 'dev' branch.

   3aa869e

   [Config] Fix Azure#34186: `az config`: Remove the blanket experimenta…

   ...

   This issue will close once commit 4c244f7 is merged into the 'dev' branch.

   4c244f7
10. Ethan Yang (necusjz)

    closed this as completedin #34194on Oct 9, 2026