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

[Aditya Pujara (a0x1ab)]

Related command

az config

Description

Fixes #34186.

Remove the blanket experimental warning.

Testing Guide

• Run az config.
• Focused regression coverage: src/azure-cli/azure/cli/command_modules/config/tests/latest/test_config.py.
• Repository CI and the authorized live-test workflow validate the published revision.

History Notes

[Config] az config: Remove the blanket experimental warning

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[Yong Zhang (yonzhan)]

az config

[Ethan Yang (necusjz)]

@Azure/x-engineering-agent plz,

1. remove the test case in src/azure-cli/azure/cli/command_modules/config/tests/latest/test_config.py, it's already covered by another framework.
2. run azdev latest-index generate, it will refresh src/azure-cli-core/azure/cli/core/helpIndex.latest.json.

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).

[Yong Zhang (yonzhan)]

Please fix CI issues

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

🟢 Approval recommended

The focused change matches the issue and includes comprehensive regression coverage.

0 open findings

What changed in this PR

Removes the misleading experimental status from the stable az config command group while retaining it for config param-persist.

Changes:

• Removes the root command group’s experimental flag.
• Updates packaged help metadata.
• Adds regression coverage for commands, errors, local configuration, and parameter persistence.

File	Description
commands.py	Marks the root config group as stable.
test_config.py	Verifies warning behavior and command functionality.
helpIndex.latest.json	Removes the experimental help tag.

🧠 Review effort: Balanced

---

Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

[x-engineering-agent]

Live test skipped

⏭️ Skipping the live test for this revision because no changed test file was found (tests/**/test_*.py).

The live-test pipeline runs only the test files a PR changes, so there is nothing to execute for this commit. A skipped live test is not a passing test result. The Agent review separately checks whether the affected command module includes focused regression tests or updated recordings. If a test file is changed in a later commit, the live test will run automatically.

Posted by x-engineering-agent (Tester)

[x-engineering-agent]

Aditya Pujara (@a0x1ab)

CI recovered; current diff is empty

Upstream CI recovered after the previous failed-CI review: 51/51 checks passed, with zero failed, cancelled, or pending checks; latest completion 2026-10-09T09:09:40Z.

Head 489f4ccfa33f262a708a4e287bb6f4b385570f83 currently has no file delta against its base. All seven review tools were accounted for and are not applicable to this empty diff. No changed-line defect or deterministic policy finding is supported. The reused live-test result is a neutral skip, not a passing run.

Please confirm whether this zero-diff PR is superseded. Any validation claim for issue #34186 should include authorized upstream verification that both broker-setting values produce no blanket warning and az config --help has no experimental group notice. Existing assertions and artifact contents alone do not prove that runtime outcome or the approved regeneration requested in human feedback.

Test validation

• Live test: Skipped: no runnable changed test files were found.
• Regression coverage: Not applicable to the changed files.

Risk assessment

1/100 · Low · Low confidence

The Low rating reflects the detected change scope with no elevated security, reliability, customer, operational, dependency, sovereign-cloud, generated-output, or cross-component signal.

• Change scope: 0 changed files, 0 changed lines (+0 / -0), including 0 production files.
• Affected components: No production component was identified.
• Risk drivers: No elevated risk signal was detected.
• Regression evidence: No production-code regression-test signal applies.
• Confidence: Low because no production changed-line evidence was available.
• Required review: No additional owning-squad review signal was detected.

Posted by x-engineering-agent (Reviewer)