Skip to content

feat: introduce content processing v2 changes#6970

Open
Shreyas-Microsoft wants to merge 46 commits into
Azure:mainfrom
Prajwal-Microsoft:psl-conprov2
Open

feat: introduce content processing v2 changes#6970
Shreyas-Microsoft wants to merge 46 commits into
Azure:mainfrom
Prajwal-Microsoft:psl-conprov2

Conversation

@Shreyas-Microsoft

@Shreyas-Microsoft Shreyas-Microsoft commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

Description

This pull request introduces several improvements and fixes to the Content Processing Solution Accelerator module, focusing on input cleanup, validation enhancements, and documentation updates. The most significant changes are the removal of certain input paths, fixes to template validation, and updates to supported resource types and documentation for clarity and compliance.

Module input and validation improvements:

  • Removed existing Log Analytics and existing AI Foundry project ID paths from module inputs and nested modules to streamline configuration and reduce unnecessary parameters. (F8c22b33L9R12)
  • Fixed module and test template validation issues, including parameter descriptions/defaults, telemetry pass-through, output naming, and test parameter alignment, improving reliability and maintainability. (F8c22b33L13R14)

Deployment and validation script enhancements:

  • Updated the GitHub Action (.github/actions/templates/avm-validateModuleDeployment/action.yml) to compile .bicep files to JSON before validation, use the resolved template path, and skip pre-validation for templates close to the 4 MB limit to avoid request size errors. [1] [2] [3] [4] [5]

Documentation and resource type updates:

  • Updated the module README.md for clarity, emphasizing AVM compliance and simplifying the introduction.
  • Added support for new Azure resource API versions in the resource type table, including Microsoft.CognitiveServices/accounts and Microsoft.Compute/proximityPlacementGroups, and removed deprecated preview versions.

These changes collectively improve the usability, compliance, and reliability of the module while keeping documentation and supported resources up to date.

Pipeline Reference

Pipeline
avm.ptn.sa.content-processing

Type of Change

  • Azure Verified Module updates:
    • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
    • Breaking changes and I have bumped the MAJOR version in version.json.
    • Update to documentation
  • Update to CI Environment or utilities (Non-module affecting changes)

Checklist

  • I'm sure there are no other open Pull Requests for the same update/change
  • I have run Set-AVMModule locally to generate the supporting module files.
  • My corresponding pipelines / checks run clean and green without any errors or warnings
  • I have updated the module's CHANGELOG.md file with an entry for the next version

Shreyas-Microsoft and others added 21 commits April 20, 2026 19:30
…etwork resource to reduce compiled template size and avoid 4MB validation payload failures.
…compiled json

- Precompile .bicep to temp .json in avm-validateModuleDeployment action and use it for Test/New-TemplateDeployment
- Reduce content-processing e2e payload by removing init/idem iteration from defaults/sandbox/waf-aligned tests
- Regenerate module artifacts via Set-AVMModule
- Skip pre-validation for near-4MB compiled templates in validate step
- Point content-processing e2e tests to main.json module artifact to reduce bicep expansion variability
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot <copilot@github.com>
@microsoft-github-policy-service microsoft-github-policy-service Bot added Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue labels Apr 29, 2026
@Shreyas-Microsoft Shreyas-Microsoft marked this pull request as ready for review April 29, 2026 10:19
@Shreyas-Microsoft Shreyas-Microsoft requested review from a team as code owners April 29, 2026 10:19
@Shreyas-Microsoft Shreyas-Microsoft marked this pull request as draft April 29, 2026 11:25
Shreyas-Microsoft and others added 2 commits April 29, 2026 18:33
Co-authored-by: Copilot <copilot@github.com>
@AlexanderSehr

Copy link
Copy Markdown
Collaborator

Hola @Dongbumlee / @brittneek, please review when you get the chance 🙏

Comment thread avm/ptn/sa/content-processing/modules/key-vault.bicep Outdated
Comment thread avm/ptn/sa/content-processing/modules/key-vault.bicep Outdated
Comment thread avm/ptn/sa/content-processing/tests/e2e/defaults/main.test.bicep Outdated
Comment thread avm/ptn/sa/content-processing/tests/e2e/defaults/main.test.bicep Outdated
Comment thread avm/ptn/sa/content-processing/tests/e2e/defaults/main.test.bicep Outdated
@Dongbumlee Dongbumlee enabled auto-merge (squash) May 11, 2026 17:25
Dongbumlee
Dongbumlee previously approved these changes May 11, 2026
auto-merge was automatically disabled May 15, 2026 11:56

Head branch was pushed to by a user without write access

Shreyas-Microsoft and others added 2 commits May 15, 2026 19:37
…over comments and redundant test params

- Remove commented-out param block in modules/key-vault.bicep (top of file)

- Remove commented-out diagnosticSettings param block in modules/key-vault.bicep

- Remove leftover scaffold comment in tests/e2e/defaults/main.test.bicep

- Drop redundant 'location' param from defaults test (RG scope already provides it)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Dongbumlee
Dongbumlee previously approved these changes May 19, 2026
Address PR Azure#6970 review comment from @AlexanderSehr: the defaults test should exercise the module's defaults, not opt-in to specific properties.

Removed from defaults/main.test.bicep:

- enablePrivateNetworking: false  (matches default, redundant)

- enableMonitoring: false         (matches default, redundant)

- enableRedundancy: true          (overrides default false)

- enableScalability: true         (overrides default false)

- cosmosDbReplicaLocation: 'canadacentral' (only required when enableRedundancy=true)

Kept solutionName (CI naming hygiene), azureAiServiceLocation (required), and gptDeploymentCapacity (quota-friendly override). The non-default flag combinations remain covered by sandbox (all-off) and waf-aligned (all-on) scenarios.
…Cosmos failover handling

- Flip enablePrivateNetworking, enableMonitoring, enableRedundancy and enableScalability defaults from false to true so the 'defaults' test scenario exercises the module's real defaults; 'sandbox' still explicitly opts out.
- Fix description of enablePrivateNetworking (was incorrectly labelled 'Enable WAF for the deployment.') and rewrite cosmosDbReplicaLocation description from Conditional to Optional.
- Harden Cosmos DB failoverLocations: when enableRedundancy is true with no cosmosDbReplicaLocation, deploy a single zone-redundant region instead of passing a null locationName.
- Regenerate main.json and README.md via Set-AVMModule and update CHANGELOG.

BREAKING CHANGE: Default values of enablePrivateNetworking, enableMonitoring, enableRedundancy and enableScalability are now true. Consumers relying on the previous lightweight defaults must explicitly set the flags they want disabled.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@AlexanderSehr

Copy link
Copy Markdown
Collaborator

Hola @brittneek & @aniaroramsft, please review when you get the chance 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants