[confcom] Fix merge conflict with new tests

[DomAyre]

Why

Recently these two PRs were merged:

• [confcom] Fix multiple issues with acipolicygen --diff #9258
• [confcom] Fix --infrastructure-svn and --include-fragments combo #9264

They conflict since one adds new expected policies and the other adds new input json, so the intersection of the two has the new input, but not the newly expected output.

This PR fixes this issue

How

• Add new expected policies for the --infrastructure-svn and --fragments-json combination in the new existing_policy cases

---

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

Note: since only test data is added, no version change is required

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[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 resolves a merge conflict between two recently merged PRs that added new test cases and expected policies for the confcom extension. The conflict occurred because one PR added new input JSON configurations while the other added expected policy outputs, creating a mismatch between input and expected output for certain test combinations.

• Adds missing expected policy files for the --infrastructure-svn and --fragments-json combination
• Ensures test consistency by providing the correct expected outputs for new test scenarios

Reviewed Changes

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

File	Description
src/confcom/samples/aci/existing_policy_allow_all/policy_fragment_plus_infrastructure_svn.rego	Adds expected policy output for existing_policy_allow_all test case with infrastructure SVN and fragments JSON
src/confcom/samples/aci/existing_policy/policy_fragment_plus_infrastructure_svn.rego	Adds expected policy output for existing_policy test case with infrastructure SVN and fragments JSON

[github-actions]

Hi @DomAyre

Release Suggestions

Module: confcom

• Please log updates into to src/confcom/HISTORY.rst
• Update VERSION to 1.3.1 in src/confcom/setup.py

Notes

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