fix: fix for quotacheck script to handle failure when quota is not available #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request updates the deployment workflow to significantly increase the minimum GPT model capacity and improves quota checking logic in the infrastructure script. The main focus is on scaling up resource allocation for GPT models and ensuring quota checks are more robust.
Resource allocation changes
GPT_MIN_CAPACITYenvironment variable from1to150in.github/workflows/deploy.ymlto support higher model capacity during deployment.GPT_MIN_CAPACITYin the workflow steps and Azure deployment command to use the new value (150instead of1). [1] [2]Quota checking improvements
infra/scripts/checkquota.sh, setINSUFFICIENT_QUOTA=truewhen no quota information is found for a model in a region, improving error handling and reporting for quota checks.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information