fix: added e2e testing in validate non waf pipeline and fixed WAF deployment pipeline

[Dhruvkumar-Microsoft]

Purpose

This pull request introduces several updates to the deployment workflows and supporting scripts to enhance model deployment flexibility, automate post-deployment tasks, and improve configuration handling. The main changes include parameterizing model capacities, updating model versions and names, adding post-deployment automation, and refining script logic for better robustness and clarity.

Deployment Workflow Enhancements

• Parameterized model capacities for GPT_MIN_CAPACITY, O4_MINI_MIN_CAPACITY, and GPT41_MINI_MIN_CAPACITY in both .github/workflows/deploy.yml and .github/workflows/deploy-waf.yml, allowing for more flexible and environment-specific resource allocation. [1] [2] [3] [4] [5]
• Updated model deployment to use gpt-4.1-mini with version 2025-04-14 and set the default image tag to latest_v3. [1] [2]

Automation and Post-Deployment Tasks

• Added a post-deployment script step in deploy.yml to automate uploading team configurations and processing sample data, improving deployment completeness and reducing manual intervention.
• Introduced an automated end-to-end test job (e2e-test) that runs after a successful deployment and before cleanup, ensuring deployments are validated before resource teardown.

Script and Logic Improvements

• Enhanced infra/scripts/checkquota.sh to support new model capacity variables, clarified required and optional environment variables, and improved model capacity mapping logic. [1] [2] [3]
• Improved input handling in infra/scripts/upload_team_config.py to better handle empty or missing user principal IDs. [1] [2]

Other Notable Updates

• Improved container app selection logic to ensure the correct backend app is targeted, excluding MCP apps.
• Updated test automation workflow to use the new accelerator name "MACAE v3".

These changes collectively improve the reliability, flexibility, and automation of the deployment process.

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