Skip to content

Conversation

@Roopan-Microsoft
Copy link
Contributor

@Roopan-Microsoft Roopan-Microsoft commented Nov 24, 2025

Purpose

  • This pull request introduces significant improvements to the deployment and data processing workflows, mainly by updating the embedding model integration to use Azure AI Foundry endpoints, enhancing deployment documentation, and adding robust packaging scripts for the web app. The changes are grouped as follows:

Embedding Model Integration and Data Processing Updates:

  • Refactored embedding generation in both infra/scripts/index_scripts/02_process_data.py and scripts/data_utils.py to use the Azure AI Foundry endpoint via the new AZURE-AI-AGENT-ENDPOINT secret, replacing previous OpenAI-based logic and dependencies. This includes switching to the azure-ai-inference library and updating secret retrieval and embedding calls. [1] [2] [3] [4] [5] [6] [7] [8]
  • Added AZURE-AI-AGENT-ENDPOINT as a new secret to the Key Vault in the deployment template (infra/main.bicep).

Deployment and Packaging Enhancements:

  • Added cross-platform packaging scripts (infra/scripts/package_webapp.ps1 for Windows and infra/scripts/package_webapp.sh for POSIX) to automate the build and packaging of frontend and backend code for Azure App Service deployment. [1] [2]
  • Introduced a new deployment configuration file azure_custom.yaml to support custom deployment scenarios, including service definitions, hooks, and parameterization.

Documentation Improvements:

  • Updated docs/DeploymentGuide.md with instructions for deploying local changes and handling Log Analytics workspace deletion when replication is enabled, referencing a new troubleshooting guide. [1] [2] [3]
  • Added docs/LogAnalyticsReplicationDisable.md with step-by-step guidance for disabling Log Analytics workspace replication before deletion.

Script Robustness:

  • Improved infra/scripts/run_create_index_scripts.sh to correctly substitute and revert the Key Vault name in scripts/data_utils.py during deployment and cleanup. [1] [2]

These changes collectively modernize the embedding workflow, streamline deployment and packaging, and provide clearer documentation for developers and operators.

Does this introduce a breaking change?

  • Yes
  • 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

  • I have built and tested the code locally and in a deployed app
  • For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
  • This is a change for all users of this app. No code or asset is specific to my use case or my organization.

Other Information

Vemarthula-Microsoft and others added 23 commits November 17, 2025 22:17
- Created PowerShell script `build-push-acr.ps1` for building and pushing Docker images to ACR.
- Created Bash script `build-push-acr.sh` for the same purpose, ensuring compatibility with Unix-like environments.
- Both scripts handle environment variables, ACR login, Docker image building, and pushing to ACR with error handling.
Added note about disabling Log Analytics workspace replication before deleting resources.
Removed note about reverting file name changes after deployment.
Updated instructions for renaming configuration files in the deployment guide.
feat: Add support for developer experience
feat: Add Troubleshooting Guide for Log Analytics Workspace Deletion Issues
@Roopan-Microsoft Roopan-Microsoft merged commit 6871b2c into main Nov 24, 2025
20 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

🎉 This PR is included in version 1.7.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants