fix: update maxReplicas to 1 for WAF deployment scaling

[Pavan-Microsoft]

Purpose

This pull request updates the infrastructure templates to improve resource stability and compatibility with newer Azure APIs. The main changes are a restriction on container app scaling to prevent excessive agent creation during WAF deployment, and a comprehensive upgrade of apiVersion references for Azure resource deployments from 2022-09-01 to 2025-04-01. Additionally, the Bicep generator version and template hashes have been updated throughout the JSON templates to reflect the new build artifacts.

Scaling and deployment stability

• The maxReplicas setting for the container app in infra/main.bicep is now hardcoded to 1 (instead of conditionally allowing up to 3), due to issues with multiple agents being created per type during WAF deployment. This change ensures more predictable scaling behavior.

Azure resource API upgrades

• All Azure resource deployments in infra/main.json now use apiVersion: 2025-04-01 instead of 2022-09-01. This affects resources such as managed identities, log analytics workspaces, application insights, virtual networks, network security groups, private DNS zones, bastion hosts, jumpbox VMs, AI services, cognitive services, private endpoints, secrets exports, and AI projects. This upgrade improves future compatibility and access to newer Azure features. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19]

Bicep generator and template hash updates

• Updated Bicep generator version from 0.37.4.10188 to 0.38.33.27573 and refreshed template hashes in multiple places within infra/main.json to match the new build outputs. This ensures consistency between the Bicep source and generated ARM templates. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Deployment dependency fix

• Corrected the order of dependencies for AI services deployment, ensuring that the aiServices private DNS zone is properly included in the dependency list.

These changes collectively improve deployment reliability, future-proof the infrastructure, and ensure alignment with the latest Azure resource specifications.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

[github-actions]

🎉 This PR is included in version 1.5.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀