fix: readme updated quota, python version recommendation, fabric deployment guide #520
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 includes updates to scripts, documentation, and deployment configurations to improve clarity, consistency, and functionality. Key changes include updates to quota recommendations, region restrictions, and deployment parameters, as well as adjustments to documentation for better usability.
Deployment Configuration Updates:
infra/main.bicepto remove unsupported regions (norwayeast,southindia).DEFAULT_REGIONSlist ininfra/scripts/quota_check_params.shto align with the updated allowed regions.gpt-4omodel option from thegptModelNameparameter ininfra/main.bicepto simplify deployment options.Documentation Improvements:
docs/DeploymentGuide.mdanddocs/quota_check.mdto suggest increasing GPT-4o-mini capacity to 150k tokens for optimal performance. [1] [2]docs/DeploymentGuide.mdto specify compatibility with versions 3.9 to 3.11.docs/FabricDeployment.mdby adding details about report usage and filtering options, while commenting out deprecated steps for Power BI configuration. [1] [2]Script Enhancements:
quota_check_params.shin.devcontainer/setup_env.shto ensure proper script functionality.Workflow Adjustments:
.github/workflows/CAdeploy.ymlby changingAZURE_ENV_OPENAI_LOCATIONtoAzureOpenAILocationfor consistency.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information