feat: quota auto validation before deployment

[Priyanka-Microsoft]

Purpose

• ...
  This pull request introduces a comprehensive set of changes to enable automated validation of AI model deployment quotas in Azure. The changes include adding pre-provisioning hooks, new scripts for quota validation, and updates to parameter files to support dynamic configurations. Below is a summary of the key changes:

Pre-provisioning Hooks for Quota Validation

• Added pre-provisioning hooks in azure.yaml to execute model deployment quota validation scripts for both POSIX and Windows environments. These hooks ensure that quota checks are performed before provisioning resources.

Parameterization for AI Model Deployments

• Updated infra/main.parameters.json to include a new aiModelDeployments parameter, allowing dynamic configuration of model deployments, including model name, version, SKU, and capacity. This file also supports environment-specific configurations for backend and frontend resources.

Quota Validation Scripts

• Added infra/scripts/validate_model_deployment_quota.sh (Bash) and infra/scripts/validate_model_deployment_quotas.ps1 (PowerShell) to validate quotas for AI model deployments. These scripts parse deployment parameters, validate required inputs, and check quota availability using Azure CLI. [1] [2]
• Introduced infra/scripts/validate_model_quota.sh (Bash) and infra/scripts/validate_model_quota.ps1 (PowerShell) to perform detailed quota checks for specific regions and models, including fallback region suggestions if the primary region lacks sufficient quota. [1] [2]

Enhanced Error Handling and Reporting

• Both the quota validation scripts and the pre-provisioning hooks include detailed error messages, usage instructions, and fallback strategies to guide users in resolving quota issues effectively.

These changes collectively enhance the robustness of the deployment process by ensuring that quota constraints are validated upfront, reducing the likelihood of deployment failures.

Please refer below screenshot
Failed

Success

CODESPACE

Failed

Success

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 1.7.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀