fix: quota check script with dynamic region handling

[Priyanka-Microsoft]

Add the variable AZURE_REGIONS_RA with the value: eastus

Purpose

• ...
  This pull request includes changes to the Azure deployment scripts and workflow configuration to improve the handling of Azure regions and environment variables. The most important changes include adding a new environment variable for Azure regions, updating the script to dynamically read regions, and ensuring all required environment variables are validated.

Changes to Azure deployment scripts and workflow configuration:

• .github/workflows/RAdeploy.yml: Added AZURE_REGIONS environment variable to the workflow configuration.
• ResearchAssistant/Deployment/scripts/checkquota.sh: Updated the script to dynamically read the Azure regions from the AZURE_REGIONS environment variable using IFS.
• ResearchAssistant/Deployment/scripts/checkquota.sh: Added validation for the REGIONS environment variable to ensure it is set before proceeding with the script.

Does this introduce a breaking change?

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.

What to Check

Verify that the following are valid

• ...

Other Information

[Copilot]

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

Comments suppressed due to low confidence (1)

.github/workflows/RAdeploy.yml:28

• [nitpick] The exported variable name (AZURE_REGIONS) differs from the pipeline variable name (AZURE_REGIONS_RA), which might cause confusion. Consider aligning these names for clarity.

export AZURE_REGIONS="${{ vars.AZURE_REGIONS_RA }}"

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀