[confcom] Add a warning and path for default change for stdio

[DomAyre]

Why

Addresses

• [confcom] Add warning when stdio enabled #9202

How

• Add an --enable-stdio arg to compliment --disable-stdio and allow users to prepare for a default switch
• In the entry point for acipolicygen and acifragmentgen warn the user if they don't include either flag explaining the risks of leaving stdio enabled, warning the default may change in the future and explaining how to avoid that issue.

---

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

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

There is no functional change (only an extra arg which currently doesn't change default behaviour) no version bump is necessary

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️confcom

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	confcom acifragmentgen	cmd confcom acifragmentgen added parameter enable_stdio
⚠️ 1006 - ParaAdd	confcom acipolicygen	cmd confcom acipolicygen added parameter enable_stdio

[azure-client-tools-bot-prd]

Hi @DomAyre,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[Copilot]

Pull Request Overview

This PR adds an --enable-stdio flag to complement the existing --disable-stdio flag and introduces a warning system to prepare users for a potential future default change from stdio enabled to disabled.

• Adds --enable-stdio argument option alongside existing --disable-stdio
• Implements warning logic when neither flag is specified to alert users about security implications
• Updates parameter handling to use a unified stdio_enabled variable instead of directly using disable_stdio

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File	Description
src/confcom/azext_confcom/custom.py	Adds stdio flag logic, warning messages, and unified parameter handling for both acipolicygen_confcom and acifragmentgen_confcom functions
src/confcom/azext_confcom/_validators.py	Adds mutual exclusion validation to prevent users from specifying both --enable-stdio and --disable-stdio flags
src/confcom/azext_confcom/_params.py	Defines the new --enable-stdio argument and updates parameter configurations for both commands

[github-actions]

• For more info about extension versioning, please refer to Extension version schema