feat: Upgrade to GPT-5.4 model and enhance ACR build process#1084
Open
Ayaz-Microsoft wants to merge 3 commits into
Open
feat: Upgrade to GPT-5.4 model and enhance ACR build process#1084Ayaz-Microsoft wants to merge 3 commits into
Ayaz-Microsoft wants to merge 3 commits into
Conversation
- Updated main WAF parameters to replace GPT-4.1 with GPT-5.4 model configurations. - Modified Bicep templates to set default model to GPT-5.4 and adjusted capacities accordingly. - Introduced new PowerShell and Bash scripts for building and pushing container images, ensuring compatibility with updated model. - Updated Python scripts for seeding knowledge bases and checking quotas to reflect new model names and capacities. - Adjusted backend environment variables and configuration files to utilize GPT-5.4 model. - Enhanced orchestration logic to leverage the capabilities of the new model. - Updated test harness to validate interactions with the GPT-5.4 model.
…upport - Updated documentation to reflect changes in image build and push process. - Modified Bicep templates to include parameters for user-assigned managed identities for ACR image pulls. - Added new PowerShell and Bash scripts for building and pushing images to ACR, replacing the previous scripts. - Enhanced app service configurations to support managed identities for ACR. - Updated JSON templates to align with new Bicep parameters and outputs.
Ayaz-Microsoft
requested review from
Avijit-Microsoft,
Fr4nc3,
Roopan-Microsoft,
aniaroramsft,
dgp10801,
nchandhi and
toherman-msft
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 default language model used across documentation, configuration files, and deployment workflows from GPT-4.1 to GPT-5.4. It also updates related environment variable names, capacity values, and deployment instructions to align with the new model version. Additionally, it improves post-deployment instructions in
azure.yamlfor both Bash and PowerShell environments.Model Upgrade and Configuration Updates
gpt-4.1-minitogpt-5.4-miniin documentation, content pack examples, and agent configuration files (.github/agents/speckit.contentpack.agent.md,content_packs/README.md,content_packs/content_gen/agent_teams/content_gen.json). [1] [2] [3] [4] [5]TRANSPARENCY_FAQS.md).Deployment Workflow and Environment Variable Changes
GPT_5_4_MINI_MIN_CAPACITYandGPT_5_4_MINI_CAPACITYinstead of previous GPT-4.1 or O4 variables. This includes changes in.github/workflows/azd-template-validation.yml,.github/workflows/azure-dev.yml,.github/workflows/deploy-waf.yml,.github/workflows/deploy.yml,.github/workflows/job-deploy.yml, and.github/workflows/job-send-notification.yml. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Deployment Script and Versioning Updates
gpt-5.4-mini), version (2026-03-17), and increased default deployment capacities where relevant.Post-Deployment Instructions Improvements
azure.yamlfor both Bash and PowerShell users, clarifying how to build and push container images and run post-deployment scripts. [1] [2] [3]Does this introduce a breaking change?
How to Test
What to Check
Validate with golden path testing
Other Information