[confcom] Fix default working_dir for Windows

[MahatiC]

---

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

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @MahatiC,
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>

[github-actions]

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

[Copilot]

Pull request overview

This PR updates the confcom extension to choose a Windows-appropriate default container working directory when an image does not specify WorkingDir, and bumps the extension version for release packaging.

Changes:

• Bump confcom extension version from 2.0.0b1 to 2.0.0b2.
• Default missing/empty WorkingDir to C:\\ when generating policies for windows/* platforms (otherwise use config.DEFAULT_WORKING_DIR).

Reviewed changes

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

File	Description
src/confcom/setup.py	Increments extension version to ship the fix.
src/confcom/azext_confcom/security_policy.py	Applies a Windows-specific fallback for WorkingDir during policy generation.

[Copilot]

The new Windows-specific default for WorkingDir isn’t covered by existing unit tests (no tests reference windows/amd64). Please add a test that exercises populate_policy_content_for_all_images for a windows/amd64 policy where the image config has an empty/absent WorkingDir, and assert that the resulting working dir is set to "C:\".

[azclibot]

[Release] Update index.json for extension [ confcom ] : https://dev.azure.com/msazure/One/_build/results?buildId=161469761&view=results